Start with the team.
Send individual or bulk invitations. See which invitations were queued, which addresses already belong and which need another attempt.
Workspace controls
Invite people, choose how they sign in and set the shared defaults. Give your workspace a clear shape as the team and its ways of working grow.
Invite the product team as members. Give workspace administration to the people who manage it.
Keep the launch work shared with its team and the private workshop with its participants.
Choose the estimation scale and eligible AI models the workspace starts with.
Bring the right people in
Invite one teammate or a group, choose Member or Admin and follow the results. Pending invitations have their own expiry and controls.
Send individual or bulk invitations. See which invitations were queued, which addresses already belong and which need another attempt.
Review pending invitations, resend one when needed or revoke it. Update member roles as responsibilities change.
Suspending a member removes current browser sessions and revokes MCP authorizations. Restoring active membership allows sign-in again; agents need fresh authorization.
Shared work, considered access
Workspace membership, project and team access, private workshops and review publication each have a purpose. Choose who can participate and who can read the result.
Explore shared contextWork keeps its owning scope and access rules. Joining the workspace is one step; access to the relevant project or team matters too.
Private refinement and retrospective rooms need explicit participation, including for administrators. Review drafts belong to their author until an edition is shared.
Agent connections follow the member’s access. Apps combine their saved grants with the owner’s current access, keeping integrations within their permitted scope.
Shared defaults
Administrators manage workspace choices together, while members keep their personal planning and account preferences.
Workflows, work types and templates give shared processes a home. Automations can handle supported routine actions once their rules have been reviewed and enabled.
Explore reusable processesHow people sign in
Offer email and password, Google or Microsoft through workspace sign-in settings. Configure the provider, enable the method and use the workspace’s invitation flow.
Keep at least one usable method enabled. Changing sign-in policy can end sessions using a disabled method, so the setup explains what needs attention.
Explore integrationsEnabled methods appear on that workspace’s sign-in page. Provider configuration and credentials belong to the workspace.
Invited members join using an enabled method. Password recovery helps an existing active member regain access.
Members manage appearance, local time, notifications and their own connections separately from workspace administration.
Know the workspace’s capacity
Admin Usage brings together current usage and effective plan allowances for seats, retained work, storage and metered features. See remaining capacity and which categories need attention.
Connected agents have no plan-based count limit. Provider charges and enabled capabilities remain separate from that allowance.
Read the workspace administration guideA few useful details
Active administrators manage membership and shared workspace settings. Project, team, document and room rules still govern the material they can access. The workspace retains at least one active administrator.
The setting controls new App creation by ordinary members. Existing credentials remain available to their owners for management or explicit revocation.
Feature availability, plan eligibility and current permissions determine which settings and admin sections appear. The workspace guides explain the requirements and the effects of each change.
COME TAKE A LOOK
Curious? Leave your email. We’ll keep you posted on early access and what’s new.