Build
Your work and the team's work
When you create a routine, skill, table, file, or conversation in Mobius, it starts as yours and private unless you deliberately choose otherwise. A shared agent does not make your conversation shared. Work the agent does inside your conversation stays with you too.
Mobius shows one of these labels anywhere ownership matters:
| Label | What it means |
|---|---|
| Only you | You own it, and only you can reach it |
| Shared by you | You still own it, and you shared it with your organization |
| Shared with group | It is shared, but the agent that contains it limits it to that agent's audience |
| Team | The organization owns it for everyone who has the required role |
| Someone else's | An administrator can govern this private configuration without reading its content |
Your role still matters. Owning a routine does not let you edit routines unless your role permits it. Ownership decides which rows are in your reach; roles decide what you may do with rows you can reach.
Mine, shared with me, and team
Lists use the same three filters:
- Mine includes your private work and work you shared while keeping ownership.
- Shared with me includes colleagues' shared work and work shared with an agent group you belong to.
- Team includes resources handed to the organization.
An agent can narrow a resource but cannot widen it. For example, a shared skill inside a four-person agent reads Shared with deal team, not shared with the whole organization. A private row stays private even when its agent is for everyone.
Share or hand over
Use Share with team when colleagues should be able to use something but you want to remain responsible for it. Use Hand over to team when the resource should belong to the organization instead.
Mobius confirms any change that expands the audience. It refuses an un-share when a wider agent still has a standing assignment to the resource, and it refuses to widen an agent until you choose what happens to every narrower row that agent could expose. Nothing becomes shared just because a related agent or resource changed.
Organization administrators can transfer configuration to another active member. The target must be a real person who can belong to the organization; agents and API clients cannot own ordinary resources.
What administrators can and cannot see
Private conversations and their output remain private from Owners, Admins, and provider technicians. They cannot discover the conversation, read its title, inspect its files, use it, or transfer it. There is no hidden support or break-glass read.
For private configuration, such as a routine, skill, table, or environment, an administrator can see its name and lifecycle metadata so they can transfer or delete it. They cannot read its instructions, rows, or activity through that administrative view.
When someone leaves, Mobius shows configuration by name and requires an explicit choice for each item. Private conversations and output appear as counts only and are sealed without exposing their names or content. Mobius records the earliest planned deletion date; automated deletion is not part of the current release.
API shape
Public resource responses use the same vocabulary as the product:
owner.kindispersonorteam;owner.idis present only for a person.visibilityisprivateororganization.containeris eithernullor the agent that further narrows reach.postureis the effective label for the current caller.
Use PATCH /v1/resources/{resource_type}/{resource_id}/ownership to share,
un-share, hand over, transfer, or detach a container. Audience-expanding changes
require confirm_audience_expansion: true. Someone outside a private row's
reach receives the same 404 response as if the row did not exist.
Exact request and response shapes are in the interactive API reference.
Next
- Decide who an agent is for.
- Learn how roles and permissions limit operations.
- See how conversations work in agent sessions.