To clean up inactive members and free collaborator slots:

1. Go to Members in organization settings
2. Review the Last Login column to identify inactive members
3. Click ⋮ for each inactive member and select Remove Member
4. Confirm the removal

This frees up collaborator slots in your plan for active team members. You can check freed slots in Resource Usage.

When a contractor's project ends:

1. Ensure all their work is reviewed and approved
2. Download any important datasets or models if needed
3. Go to Members and locate the contractor
4. Click ⋮ and select Remove Member
5. Confirm the removal

Their annotations and training runs remain accessible—only their access is revoked.

When team members leave your organization:

1. Coordinate with team leads to identify work in progress
2. Reassign or complete any pending tasks
3. Transfer dataset ownership if they were the sole owner
4. Go to Members and remove the departing employee
5. Update secret keys if they had API access

This ensures business continuity while revoking access promptly.

To clean up pending invitations:

1. Go to Members in organization settings
2. Look for members with Invited or Pending status
3. Click ⋮ for members who haven't accepted after a reasonable time
4. Select Remove Member to revoke the invitation

This frees collaborator slots for members who will actually join.

To modify a member's organization role or project access:

1. Note their current datasets and training projects (click View Details)
2. Go to Members and click ⋮ for the member
3. Select Remove Member and confirm
4. Immediately re-invite them with updated roles and access
5. Notify the member to accept the new invitation

Their previous work remains intact, but their access changes according to the new settings.

Quarterly access audits:

• Review the members list every 3 months
• Check Last Login times to identify inactive users
• Remove members who have left the organization or project
• Verify active members still need their current access levels

Regular reviews prevent access creep and maintain security.

Create offboarding checklists:

• List steps to take when members leave (review work, transfer ownership, remove access)
• Assign responsibility for removing access (HR, team lead, or IT)
• Set timelines (e.g., remove access within 24 hours of departure)
• Include notifications to remaining team members

Formal procedures ensure prompt, consistent access revocation.

Notify affected members:

• Inform members before removing them (when appropriate)
• Explain why access is being revoked
• Provide time to download personal work or notes
• Offer to reconnect them if circumstances change

Professional communication maintains positive relationships.

Optimize plan usage:

• Check Resource Usage to see available collaborator slots
• Remove inactive members before adding new ones
• Upgrade your plan if you frequently hit collaborator limits
• Track removed members to understand turnover

Efficient slot management avoids hitting plan limits unexpectedly.

No—you cannot "undo" a removal. However, you can re-invite the member with the same or different access settings. They'll need to accept the new invitation.

All their previous work (annotations, runs, models) is still available since removal doesn't delete data.

Datasets themselves are owned by the organization, not individuals. When you remove a member who had Owner role on datasets:

• The datasets remain in your organization
• Other members with Owner or Admin roles retain full access
• You may want to explicitly assign ownership to another member

Dataset access continues uninterrupted.

Training runs continue normally and remain accessible:

• In-progress runs complete as scheduled
• Completed runs and their models remain available
• Metrics, logs, and deployments are unaffected

Only the member's access to view or manage runs is revoked.

Yes. Activity logs and audit trails preserve removed members' actions. You can:

• View annotations created by them (with attribution)
• See training runs they started
• Access models and deployments they created
• Review audit logs showing their historical activity

Work attribution is permanent even after removal.

Admins and Owners receive notifications when:

• A member leaves voluntarily (self-removal)
• An admin removes another member

Regular Members do not receive removal notifications.

No. The Owner role cannot be removed by other members. If the Owner needs to leave:

1. Contact Datature support at [email protected] to request an ownership transfer
2. Provide the email address of the member who will become the new Owner
3. After the transfer is complete, the former Owner can be removed or downgraded to another role

Ownership transfers must be handled by Datature support to ensure every organization always has an Owner for billing and account management.

Removal is immediate:

• Member loses access within seconds
• If they're currently logged in, they're logged out of your organization
• They cannot start new actions or view resources
• In-progress uploads or runs they started continue to completion

Access revocation is real-time and cannot be delayed.