What is private and what is shared with your team

Ampere is organized around an Organization, so teammates share some resources while other details stay access-controlled. The main distinction is between an Organization-visible record—such as a task, monitor, or alert—and the private prompt, run output, or Ampere session behind it.

Billing credits are shared across the Organization. Access to a specific session, Project Asset, scheduled execution, or monitoring follow-up depends on that resource's ownership and sharing controls.

Use this article to understand what a teammate can discover, what they can open, and which changes affect the whole Organization.

Shared Organization records

Organization settings, roles, billing, credits, and many Project-level resources belong to the Organization. Teammates with access to the current Organization can also use shared management surfaces for Scheduled Tasks and Monitoring.

The visibility of a record does not automatically expose every private detail behind it:

Ampere checks organization membership and resource access when someone opens a detail view. A link or visible name is not a new permission grant.

Scheduled Tasks: shared envelope, private execution

Scheduled Tasks use a shared Organization envelope so teammates can understand what recurring work exists. The shared view can show the task name, task type, schedule, status, run count, recent or next run timing, and an execution-availability state.

The task's execution owner controls its private execution details. Other Organization members do not receive the saved prompt or form inputs, private run messages, output references, or approval payloads through the shared envelope.

Available actions depend on ownership, Organization role, and task state. The execution owner can work with private task details when execution remains available. Organization owners and admins have governance controls for tasks they do not own, such as pausing, canceling an active run, managing recipients, archiving, or taking over a task when the current UI offers that action. Taking over changes execution ownership; it should not be treated as a shortcut for quietly reading another person's private configuration.

Use the action labels shown for the selected task as the current source of truth. If an action is absent or unavailable, the current user, task state, or execution ownership does not allow that action.

Monitoring: shared monitors and alerts

Monitoring is an Organization surface. Organization members can review the Organization's monitor inventory, health and check history, and alerts that belong to the current Organization. An alert can include the monitor name, detected change, source evidence, status, follow-up summary, and email-delivery outcome when available.

A monitoring alert may link to an Ampere follow-up. The alert and its safe follow-up summary can remain visible even when the underlying Ampere session is restricted. Ampere checks the viewer's session access before returning the follow-up session and its private output. If access is restricted, ask the session owner to share the session at an appropriate level rather than forwarding a private session link.

Alert read state is personal; resolution is shared

Monitoring keeps two different kinds of alert state:

• Read or unread is personal to each Organization member. Marking an alert read clears it for you, not for everyone. Another teammate can still see the same alert as unread.
• Open or resolved is shared for the Organization. Resolving or archiving an alert changes its lifecycle for teammates, and reopening it returns it to the active inbox.

The alert detail can show who resolved or archived it. Resolve an alert when your team has reviewed or acted on it; use read/unread when you only want to manage your own attention.

Ampere sessions use explicit access roles

An Ampere session has its own transcript, Workspace, generated files, and context. The session's Manage Access dialog can assign an Organization member No access, View, Edit, or Owner, subject to the roles the current user is allowed to grant.

• No access means the member cannot open the session through that sharing grant.
• View is for reviewing the shared session.
• Edit allows the member to work in the session where supported.
• Owner transfers the highest session access level available in the dialog.

Share a session deliberately. Review its transcript and files before granting access when the chat includes sensitive prompts, uploads, customer information, drafts, or internal notes.

Projects and Project Assets

Project context and saved Project Assets are durable project resources. They are designed to be reopened, searched, reused, and supplied as context to later work by people who can access the relevant project surface.

Some supported asset kinds can be shared organization-wide. When an asset is marked as organization-shared, treat it as visible reusable context for teammates who can access that shared asset surface. Uploaded files or project-only assets can retain a narrower scope.

Saving an output as a Project Asset changes where it can be discovered and reused. Do not save chat-only material into a shared project unless it belongs in that team's durable context.

Credits and billing access

Ampere messages, AI Tool and workflow runs, Scheduled Task runs, browser sessions, and select background AI work use the organization's shared credit pool. Adding a teammate does not create a separate personal credit balance.

Shared credits do not mean every teammate can manage billing. Billing access is separate: Organization owners and designated billing admins can access billing management. A low or exhausted Organization balance can affect new billable work across the Organization even when a teammate cannot open the billing page.

Good privacy habits

Before you share a session, save a Project Asset, configure recipients, or create recurring work:

• Remove content that does not belong in the Organization.
• Check the selected organization and project.
• Review session access and execution ownership.
• Treat alert resolution as a team-wide action and read state as personal.
• Do not put passwords, private tokens, billing card details, secret keys, or unnecessary personal data into prompts, files, tasks, monitors, or saved assets.

When in doubt, assume Organization records can be discovered by organization members, while private execution and session details remain available only through their specific access controls.