Workspace roles and permissions

What someone can do in Helpin depends on three things: their workspace role, the teams they belong to, and the modules they have access to. This article explains each one so you can give people the access they need.

Workspace roles

Every member has one workspace role. You choose it when you invite someone and can change it later in Settings > Members.

Role	What they can do
Owner	Everything an Admin can do, plus delete the workspace, remove connected integrations, and make other people Owners
Admin	Full access across all teams. Manage workspace settings, members, invitations, teams, module access, integrations, workflows, labels and automations. Administer Docs, CRM and Support
Member	Create and edit work in their teams, and create, edit and publish documents. Work in CRM and Support when they have access to those modules
Viewer	Read-only access to tasks, epics and sprints in their assigned teams, and to the other modules they can open

All roles can search the workspace and manage their own notifications.

Teams

Teams control which project work Members and Viewers can see. Members and Viewers work with the tasks, epics and sprints of the teams they belong to. Owners and Admins can see every team.

Inside a team, a Member can be made a Team Manager. Team Managers can manage their team's settings and members, and they can manage sprints and objectives for their team. See Manage team membership.

Module access

Module access decides which modules appear in someone's sidebar.

Module	Who has access
Projects and Docs	Every member of the workspace
CRM, Support and Automation	Owners and Admins always. Other members when an Admin grants the module to one of their teams or to them directly

Admins grant module access in Settings > Module access, by team or by person. You can also see and change a person's module access when you edit them in Settings > Members.

Module access and roles work together. Access to a module lets someone open it. Their role then decides what they can do there. For example, a Viewer with Support access can read conversations but can't reply.

Notifications follow the same rules: people aren't notified about modules they can't open.

Choose the right access

• Give most people the Member role and add them to the teams they work with.

• Use Viewer for people who need to follow along but shouldn't change anything.

• Keep the Admin role for the people who manage settings, members and integrations.

• Grant CRM, Support and Automation to teams rather than individuals, so access follows team membership.

Related

• Invite and manage workspace members

• Manage team membership

• Module access control