Membership gives someone an ongoing role in a Workspace. A resource invitation gives them access to particular work. Choose the narrower relationship that fits the collaboration rather than granting organization-wide participation by default.
Choose the invitation
| Need | Use |
|---|---|
| Adopt a reusable starting point | Marketplace remix |
| Collaborate on an individual resource | Resource invitation |
| Ongoing organizational participation | Workspace membership |
| Use a released Site | Its visitor audience and any application login |
Review the role and scope before sending an invitation. The recipient accepts the invitation before its grant takes effect. A role on one resource does not expose its siblings or automatically authorize connected accounts.
Manage participation
Use Workspace Members to inspect organizational roles and the actions available to your role. Keep ownership, administration, editing, and viewing responsibilities distinct. For a specific resource, use its own sharing controls.
A shared Artifact does not reveal the source conversation. A Site visitor does not become a source editor. Membership administration also does not grant unrestricted access to private content.
Handle departure carefully
Deactivation or departure removes Workspace access. Owned resources remain in Workspace custody; ownership and historical authorship do not disappear merely because membership changes.
When continuity requires it, the Workspace Owner can use the supported reassignment workflow for a deactivated member's resources. Before permanent removal, reassign every resource you need to keep. Permanent removal deletes all resources the member still owns, bypasses retention, and cannot be undone. Their account and other Workspaces are unaffected. Reactivation does not automatically restore previously revoked direct grants or reassigned ownership.
The owning Workspace pays for authorized shared use without a seat fee or per-person credit grant. See Permissions, Budgets, and Lifecycle.
Roles
Choose a role according to the responsibilities the person needs in this Workspace. For Workspace-visible resources, that role can also provide resource access. Review inherited permissions before confirming an invitation or role change.
For a consultant working on one resource, consider a resource invitation instead of Workspace membership. Review explicit resource invitations separately when someone’s responsibilities change.
The shared model is explained in Permissions. Use Agent access for application grants, Site access for production audiences and management, and Connections for external accounts. Enterprise covers organizational policies and their current limits.
Example: a colleague changes responsibilities
When a colleague moves from building a Project to reviewing its results, inspect their Workspace role and explicit resource grants. Adjust the relationships that actually provide access instead of assuming one role change removes every permission.
Review owned resources and any required continuity before deactivation or permanent removal. See Lifecycle.
Review an invitation
Confirm the recipient, the Workspace or resource being shared, and the role before sending. After acceptance, check the resulting membership or grant rather than treating an email delivery status as proof of access.
For example, a consultant reviewing one portal can receive a Project invitation. A colleague responsible for ongoing organizational work may need Workspace membership. Neither choice automatically supplies production authority or an external account connection.