Choosing an organization model
Keep organizations aligned with real trust boundaries. Use one organization for a team that can safely share inventory, memories, procedures, and session context. Use separate organizations when customers, business units, labs, or regulated environments should not see each other’s work.| Scenario | Recommended shape |
|---|---|
| One internal network team | One organization. |
| Consultancy serving multiple customers | One organization per customer, plus an internal organization. |
| Production and lab are operated by the same people | One organization with folders and visibility controls, unless secrets or compliance require separation. |
| Separate business units with different admins | Separate organizations. |
| Vendor access for one incident | Guest session link, not organization membership, unless ongoing access is required. |
The organization switcher
The organization switcher sits in the lower-left of the activity bar. Clicking it lists every organization you belong to along with a shortcut to create a new one. Picking an organization re-signs you in against it and re-scopes everything in the workspace — your host tree, your chats, your procedures, your memories, and your dashboards all refresh to the new organization’s content. If you’re working with a customer and your own team in the same week, it’s normal to flip between organizations several times a day. Studio keeps your layout and unsaved work where it is; only the scoped data changes. Before running a procedure or changing inventory, glance at the organization name in the shell. It is the fastest way to catch “right host, wrong customer” mistakes.Visibility: private versus team
Every item you create in Studio is either private to you or shared with everyone in the organization. The toggle lives on the item itself.| Item type | Private | Team |
|---|---|---|
| Hosts | Only you see them. | Everyone in the organization sees them. |
| Diagrams | Only you. | Everyone in the org. |
| Procedures | Only you can run. | Anyone in the org can run. |
| Memories | Your recall only. | Shared org knowledge. |
| Conversations | Private by default; can be shared on request. | N/A. |
| Keychain entries | Always private to you. | N/A. |
Roles
Each member of an organization holds one role. The role determines what they can change.| Role | Can do |
|---|---|
| Owner | Everything, including billing and deleting the organization. |
| Admin | Manage members, manage team items, invite and remove users. |
| Member | Create and edit their own items, see team items, run procedures. |
Team hygiene
- Keep shared host names and folder names consistent; search quality depends on the names people remember.
- Review shared procedures before marking them active.
- Use memories for durable operational facts, not personal notes.
- Keep credentials in each user’s Keychain instead of sharing raw secrets in chats or memories.
- Remove inactive members from the dashboard when they no longer need access.
Inviting and removing members
Invites and user management happen in the Altostrat dashboard, linked from the organization switcher. An admin or owner can invite a teammate by email, set their role, and remove them when they leave. Because Studio re-scopes on sign-in, a newly invited teammate sees the organization’s team items the first time they pick it from the switcher.Presence and collaboration
When teammates are signed into the same organization, Studio surfaces their presence on shared surfaces — you can see who is viewing a shared terminal, who is joined to a call, and who is active in a session. For real-time work like pair troubleshooting, handoff, and voice or video in the middle of a session, see shared-sessions.Related
Shared sessions
Bring a teammate into a live terminal with owner, co-work, or viewer roles, and promote to voice or video without leaving.
Security and privacy
Understand what’s encrypted, what stays on your machine, and what happens when you sign out.