Team Ownership · AlefOS Documentation
One person owns the customer. The right teammates can still help.
Team keeps responsibility clear with a primary assignee, a shared company queue for unassigned work, and section-level collaboration for teammates who need to contribute without taking ownership.
Visible ownership · Precise permissions · Every assignment and revocation is audited
Marc Dupont · Customer file
TeamPrimary owner
Sarah owns the relationship and the next customer action.
Contributor
David can contribute to notes only. He cannot act as Sarah.
Next mission
Send the revised proposal before Friday.
Ask AlefOS
Who owns Marc, and who can help?
One customer, clear responsibility
Work moves. Ownership stays understandable.
A customer can enter through the company queue, move to a primary owner, receive help from a collaborator, and finish with the owner validating the next action.
Nothing disappears
New or unassigned work remains visible until somebody takes responsibility.
Responsibility is explicit
Sarah becomes the customer owner and carries the relationship and next actions.
David helps precisely
David receives contribution access to notes without taking over the customer.
Sarah keeps control
The owner reviews the follow-up and remains visible as the responsible person.
Team collaboration never means impersonation. Ownership stays visible, permissions remain precise, and every assignment or revocation is audited.
Three states everyone can understand
Responsibility does not have to be hidden inside a conversation or remembered by a manager.
Company queue
New, released or temporarily unassigned work stays available to the authorized company scope.
Primary owner
One member is clearly responsible for the relationship, the mission or the calendar event.
Collaborators
Teammates receive observer or contributor access only to the sections they need.
From blurred responsibility to visible action
The team can help each other without turning every customer file into a shared free-for-all.
Before
People ask who owns the customer, duplicate follow-ups, or assume somebody else will act.
With AlefOS
Ownership, collaboration scope and pending work are visible from the same operational memory.
Result
The right person stays accountable while authorized teammates remove blockers faster.
Ask responsibility directly
AlefOS can answer ownership questions and prepare explicit assignment or collaboration changes.
Control points
The ownership model is explicit, reversible and designed for permission-based company work.
Assign, reassign or return to the queue
An authorized Team member can assign or reassign a contact, mission or calendar event. Removing the assignee returns the item to the company queue instead of making it disappear.
Every change preserves a visible responsibility state and is recorded for audit.
Observer and contributor roles
A collaborator can be added as an observer or contributor. Observer access is read-only. Contributor access allows help only inside the granted sections.
The primary owner remains the owner. A collaborator never silently takes over or impersonates that person.
Section-level permissions
Collaboration can be restricted to exact sections such as notes or calendar context. The company can grant only what the teammate needs instead of opening the entire customer file.
Expiry and revocation
Collaboration access can include an expiry date and can be revoked when the work is complete. Granting, changing and removing access are audited.
MCP tools
Team ownership is available through protected MCP tools for contacts, missions and calendar work:
contacts.assigncontacts.collaborators_listcontacts.collaborator_setcontacts.collaborator_removemissions.assigncalendar.assign
Permission checks and audit trails still apply when the action starts from an assistant.
Choose your next step
Give every customer a clear owner without closing the door on teamwork.
Talk with AlefOS about roles, assignment rules, collaboration scopes and Team deployment.