Help center
Help center
AI SORTIFY · GUIDE

How does team access work?

Invite people to your workspace and give them the access their work needs.

Invite a teammate

  • Open Team and choose the invitation action.
  • Enter the intended email and review the available role or permissions.
  • Send the invitation and check its status in the member list.
  • The invited person must accept the invitation before joining.

Read invitation status

Pending invitations are waiting for acceptance. An expired invitation needs to be resent using the available action. Check the email address before resending; resending sends another real invitation.

Roles and permissions

A role and its permissions control available workspace actions. Review the permissions shown in the app instead of assuming every teammate can manage settings, rules, or other members. Owners manage invitations; member-management actions can also be available to administrators.

Capacity and access

The capacity display shows used and available teammate slots for the current plan. If no slot is available, review existing members and the plan before inviting someone else. The owner has protected management behavior and cannot be blocked like an ordinary member.

Block or remove a member

Use the member actions to review the available access changes and their confirmations. Blocking access and removing membership are different operations. Review who is affected before confirming.

A shared workspace

Team members work with the organization’s documents and configuration according to their permissions. Changing your personal account details is separate from changing the organization’s shared details.

Resend, block, restore, and remove

  • Send invitation again sends a new invitation email to the shown address. Confirm that address before sending.
  • Block access signs the member out and prevents workspace access until restored.
  • Restore access allows a blocked member to access the workspace again.
  • Remove is a separate membership action with its own confirmation.
  • Self, owner, missing-user, role, and pending-action restrictions can disable controls. A disabled button is not evidence that the action already happened.