Sharing Resources
Secoda is built to be collaborative, so there's a number of ways to share content and resources with other people.
How to share resources in Secoda
There are a few different ways that you can organize permissions in Secoda. Entities will inherit permissions from their parent, so if you give someone access to a Team, they will have access to all of the resources within that Team. If you give someone access to a Collection, they will have access to all of the resources within the Collection. If you give someone access to a resource, they will have access to that resource only.
Teams permissions
Teams are the highest level of organization in Secoda. You can create teams for different departments, projects, or any other way that makes sense for your organization. You can then assign resources to teams, and all members of that team will have access to those resources.
Collection permissions
Collections are a way to organize your resources within a team. You can create collections for different projects, or any other way that makes sense for your organization. You can then assign resources to collections, and all members of the Team that collection is in will have access to those resources.
Group permissions
Groups are a way to organize the members within your workspace. It's common to create groups so that it's easier to assign ownership at the Group level, or add Groups to Teams instead of individually adding users to a Team one-by-one.
Entity-level permissions
You can edit inherited permissions (permissions based on Teams) by clicking Share in the top right of your resource.
Clicking Share opens up existing Permissions (Image 1). In the case below, the Collection is shared with all users in the General Team.
To remove select users from viewing this Collection, but keep them in the Team, you can click "Can read" and select "Remove access" (Image 2).
After removing the user, you'll see "Reset permissions" appear (Image 3). This button is helpful if this was done in error, or if you'd like to re-open up access to those users.
Clicking Copy link copies the resource's unique URL to your clipboard so that you can share it with whoever you want. Still, only people with access to the resource can see it.
If a parent document or a Collection has custom entity-level permissions set, users who are not in that permissions set will not be able to access anything nested within it.
Make sure that when you're sharing a resource with someone, if it's nested in a Collection or under a Parent document, that parent resource permissions include the user you're hoping to share it with.
Last updated
