Roles determine which features users can access in Teamdash. By default, every organization has three roles: Administrator, Regular User, and Limited User.

Access role management by navigating to Organization Settings → Roles. Administrators retain the flexibility to modify existing role permissions or establish new project-based roles tailored to organizational requirements.

The Administrator has full access to all Teamdash features and settings. In addition to managing recruitment projects, administrators can configure organization settings, manage users, roles, and tags, and access every system feature.

This role is generally intended for the people responsible for administering Teamdash within your organization.

The Regular User is typically a recruiter or HR specialist with access to nearly all recruitment-related features. They can create and manage projects, add candidates, invite new members to projects, and manage the entire recruitment process.

By default, a Regular User does not have access to:

The Limited User role is primarily intended for hiring managers or clients who participate in the recruitment process but do not require access to the entire system.

By default, a Limited User can only view projects they have been added to as a member. They can also only access candidates associated with those projects and cannot access the organization's full candidate database.

Within the candidate profile, they can view:

When adding comments, users can choose whether the comment is public or private. Limited Users can only see public comments.

By default, a Limited User can:

The permissions described above are only the default configuration. Administrators can customize the permissions of all three roles to fit their organization's requirements.

Permissions are organized into categories such as Projects, Landings, Candidates, Job Profiles, Requisitions, and many others. Each permission can be enabled or disabled individually, allowing you to create highly customized access levels.

Project Roles grant expanded permissions within specific projects without modifying organization-wide access. For instance, a Limited User might receive messaging permissions for one recruitment project while retaining global restrictions elsewhere.

Create a Project Role from the Roles menu by selecting Create role, then Project role, entering a name, and selecting the appropriate permissions.

Assign it to users through Manage Project Access within the relevant project.

At the bottom of the role settings, you'll find Administrative Permissions. These permissions provide access to organization-wide settings and system administration features.