Workspace access and account boundaries

Open the workspace from the selected Aortem organization and use its Google account. A Google session alone does not grant access to an organization. An account outside that organization is denied access to its repository and drafts.

Suite membership and an existing standalone product account are separate. Matching email addresses do not link organizations, subscriptions or repository permissions automatically. Contact customer support to resolve unexpected access before creating a duplicate organization.

Owners and admins can import repository text, edit Markdown drafts and remove saved content. Viewers can read the workspace. Changing organization membership or application access is managed through the Aortem console rather than by editing a draft or choosing another filename.

Import only text you are authorized to share with your organization. The Standard workspace stores a manual snapshot independently of the original Git repository. Removing that snapshot also removes its saved drafts, but does not change the original repository. Download content you need before confirming deletion.

Give support the product, page URL and error message. Do not send passwords, API secrets or access tokens. For developer integration authentication and service boundaries, see Product AI integration.

This guide explains product access behavior; it does not replace your applicable privacy policy, security agreement or service contract.