Account
Team Members
Invite members, manage roles and resource access, and remove access when someone leaves.
Team Members
Invite members, manage roles and resource access, and remove access when someone leaves.
Where to find it
Open Account > Team Members.
Address: /account/members.
Invite or select a member
To invite someone, choose Add member, enter Email, review Access type, memory access, and product roles, and choose Send invitation or Authorize chat access as offered. Then open the intended person or invitation in Team Members. Chat only is for enabled external chat without the web workspace or builder. Review the invitation identity before resending an existing invitation.
Save roles and memory access
In the member's access settings, choose product roles and set Read organizational memory and Contribute to organizational memory independently. Choose Save access to commit these settings. Field changes remain staged until saved. Turning contribution off does not erase previously accepted memory or otherwise authorized chat access.
Save workspace and app grants separately
Use the direct-share toggles for the intended workspaces/apps, then choose Save access only. This is separate from saving product roles and memory access. New direct app grants here are Viewer. This panel does not offer an Editor role selector; use the resource's Topline sharing controls for collaboration roles. Saving sends no email and does not publish drafts.
Read the per-resource outcomes: some writes may succeed while others fail. Reconcile the saved grants before retrying failed items. Removing a direct grant may leave owner, account, scope, or inherited workspace access in place. Verify one intended and one prohibited resource after changing access.
Archive or restore access
Archive member removes Topline access and signs the member out. Unarchive member restores the member's active status when offered; inspect current roles and independent grants afterwards rather than assuming the desired access. Offboarding also requires reviewing owned credentials, MCP access, and external-provider access; archiving a member does not itself revoke a provider credential.