Use one account per person
Invite each teammate and have them sign in with the invited address. The owner can invite from a connected chat (that invite tool is owner-only and invites people as members) or through the account site, where an account-site admin can also invite. New members usually appear in the Mind within about 20 minutes. Join a team explains the first permitted task to check after joining. Do not share the owner’s login to make a connection work.
The Mind records the identity used for a request. That is useful when checking who suggested or approved a change, but the recorded identity does not prove every statement in the changed record is true.
Separate roles from effective access
Owner, admin and member describe management authority. The owner controls the workspace and can delegate particular administrative jobs. An admin does not automatically receive every management permission.
Profiles group areas of information for a job. Defaults and other grants can contribute to what a person actually sees. Roles, profiles and effective access explains why a role or profile name alone is not the final check.
Share a source rather than a login
Keep the common decision in an area the intended people may read. Link to it from the handoff and identify the work still open. Each colleague and their agent reads it with their own access. Share work without sharing everything explains what to include.
Review changes under the right authority
Reading, proposing and approving are separate permissions. The Mind’s settings decide whether an eligible proposal saves immediately or waits for a reviewer. Review rules explain that outcome; review requests explains choosing the relevant human action.
Check changes to access
When a person joins, changes jobs or leaves, inspect the resulting access and check a harmless task as that person. Change or remove access explains profile changes and the separate steps needed for a full departure.
Related
Practical guides for people and agents