Sharing and permissions

Everything in Mycorr is private until you share it. You give access at one of three levels: a space, a model, or a single table. Pick the narrowest one that does the job.

Three ways to give access A role on a space reaches every model in it, live. A direct share on a model reaches that one model, live. A share on a table lets someone import its release into a model of their own, read-only. ROLE ON A SPACE Sales Pipeline Forecast Accounts Every model in the space Manager, Collaborator or Viewer. Live work, and models added later. SHARE A MODEL Sales Pipeline Forecast Accounts One model Collaborator or Viewer. Live work, nothing else in the space. SHARE A TABLE Pipeline Orders Their model Orders release One table, in their own model Can Import or Can Share. The release, read-only.
A space or model share lets people into live work. A table share only ever hands over a release, into a model of their own.
ShareYou giveThey getUse it for
A spaceManager, Collaborator or ViewerEvery model in the space, live, including models added laterA team that works together
A modelCollaborator or ViewerThat one model, liveBringing someone into one piece of work
A tableCan Import or Can ShareThe table's release, imported read-only into their own modelsGiving another team data they build on

Sharing a space or a model lets people into your work in progress, and they see changes as they happen. Sharing a table never does: they read what you have released, and your next edits do not reach them until you release again.

Who you can share with

  • In your personal organization, you can share with anyone by email. Someone without a Mycorr account gets an invitation, and their access is waiting when they sign up.
  • In any other organization, you share with its members. An address outside it is refused with Not a member of …: invite the person to the organization first.
  • In a Sealed space, nothing is shared one model or one table at a time. Access comes from the space alone.

People you share with get a notification in Mycorr, and an email with a link, depending on their notification settings.

Seeing a table and reading it

Mycorr separates knowing a table exists from reading its data. You can see a table in a model, on a canvas or in a link, without being allowed to read its rows: for example, a table imported into a model you view, from a model you have no access to.

When that happens the table shows a chip: No access to this table's data — click to request it. Click it, and the table's owners get a request; the chip then reads Access requested. Exports, downloads and AI assistants follow the same rule: if you cannot read a table's values, none of them can read them for you.

Requests and notifications

When someone asks for access, the people who can grant it get a notification with Accept and Decline. Table owners also see waiting requests under Import Requests in the table's details.

Notifications in the sidebar collects every invitation, request and share, with All and Unread tabs and filters for Requests and Updates.

Shared with me

Spaces and models shared with you from an organization you are not a member of appear under Shared with me in the sidebar. The item shows up only when there is something there.

Revoking access

Owners can remove anyone they gave access to, at any time, from the same Manage access list with Revoke Access. The change takes effect at once, including for AI assistants and tokens acting for that person.

If the person had imported one of your tables, the import becomes a read-only stub: it stays on their canvas, marked as no longer accessible, without its rows.

Moving data between organizations

Data in an organization other than your personal one stays inside it: its tables cannot be shared with or moved to another organization, or published to the public catalog. Within an organization, you can move a table to another model you own, and move a model to another space you manage.