Organizations
Invite people and organize teams.
In Siglata, each person in the organization has a role, such as owner, admin or member, and their agent works only within that role and the files and folders the person can open. Owners and admins invite members, change roles and organize teams through the agent.
An organization has as many members as it needs. The agent invites, lists and removes members and changes their roles with invitation_create, invitation_cancel, members_list, member_update_role and member_remove, and also renames the organization. To leave or delete the organization, use the Console’s Account page.
Teams
Owners and admins group members into teams and share files and folders with a whole team at once.
- The agent creates, renames and deletes teams and checks who is on each one with
teams_list,team_setandteam_delete. - An organization starts with no teams, and a member can be on several.
- Grant a folder or file to a team with
grant_setandgranteeType: "team". Access follows the team’s current members: whoever joins opens what the team was granted, and whoever leaves stops on their next request. If Siglata cannot confirm which teams someone is on, the request is refused.
Common questions
Can the agent see files I can’t open?
No. The agent uses the role and access of the person who approved the connection. A restricted item you can’t read doesn’t show up in your agent’s listings either.
Who can invite or remove members or change roles?
Owners and admins, with the members:write scope approved on the connection. A person with the member role can’t run these operations, even if the connection asks for the scope.
What happens when someone leaves the organization?
The files stay in the organization, and the connections of that person’s agents stop working on the next request.
How do I give a whole team access to a folder?
Ask the agent to grant the folder to the team. It uses grant_set with granteeType: "team", and whoever joins the team later can open the folder. See Folders and access control.