Groups
Groups let an admin grant a set of people shared access to files and folders without assigning them the same workspace role.
Category
Governance
See all terms
What are Groups in Qontext?
A group is a set of people who share access to files and folders without needing to hold the same workspace role. An admin creates a group, adds the relevant members to it, and then grants that group access to a file or folder the same way they'd grant it to an individual member. Every member of the group inherits whatever access level the group holds.
Why do Groups exist?
A workspace role sets someone's baseline permissions across the whole workspace, but a team working on one project or client rarely maps cleanly to a single role. Without groups, giving five people shared access to the same folder means either repeating the same grant five separate times or changing everyone's workspace role to something broader than the job needs. Groups exist so scoped, project-level access doesn't have to route through a formal role at all: an admin defines the group once and manages its access as a single unit, adding or removing members without touching anyone's role or repeating the grant per person.
How do Groups work?
An admin creates a group and adds or removes individual members from it. That group can then be granted access to any file or folder in the context repository, through that item's access management section, the same way a user or an API key would be added there. Access still resolves as a chain, workspace baseline, then parent folder, then the file or folder's own setting, so a group's grant follows the same widen-only rule as any other access control: it can extend access deeper in the tree but never narrow what a higher level already granted. Groups sit alongside user permissions and API key permissions as a third way into the context repository, letting an admin manage a whole team's access as one unit.