Who can read and contribute?
Project Aurora collection
PersonReadWrite
Camila
Bruno
Pedro—
Partner—
Every access has a scope.
Read and write are separate permissions. Define what each person can do with a collection's context.
PermissionsShared context.
Shared context.
Access you control.
Choose who can read and who can contribute. Each collection has its own authorized people and connections.
1CamilaClient service · read and write
2BrunoOperations · read and write
3PedroCoordination · read
+Invite someone
You choose who takes part.
Share knowledge with authorized people without opening every collection to everyone.
Set access
Read contextRead permission
Save lessonsWrite permission
Connect your AIAccess set per collection
Your AI respects access rules.
The connection reads authorized context. Sharing memory does not mean sharing every conversation.
Your context can be shared.
You stay in control.
Access per collection
Each collection has its own authorized people and connections.
Chosen members
Share context with the people involved, within or outside your team.
Read permission
People with read access can retrieve knowledge already saved in the collection.
Write permission
People with write access can add decisions, references and new lessons.
Authorized connections
Your AI accesses the context available to the connection you configured.
Shared control
Each person keeps their own AI, respecting each collection's access rules.
Your team already has the context. Move every conversation forward.
1
Shared memory
2
Access levels: read and write
3
Steps: account, collection, connection
∞
Ways to keep going