Recruitment Marketing: User Roles

Recruitment Marketing Public

So that your Recruitment Marketing content can be distributed with confidence and be effective in attracting, engaging, and informing candidates, it must meet the branding standards set by your organisation. 

Recruitment Marketing has a content approval mechanism in place that helps reduce the risk of substandard content going live. Each team member has specific content access rights or publishing permissions assigned to them. These rights and permissions are determined by the user roles. A user's role allocations apply across all company accounts.

Supplementary information:

Organisation Admin

This is a system account administrator. This user has access to all data and functions (including the Integrations section), as well as the ability to manage users, manage themes, and organise companies.

Anyone who is an Organisation Admin can assign this role level and the following roles.

Company Admin

A company account administrator. This user has access to all data and functions (including the Integrations section) within a Company. 

Anyone who is a Company Admin can assign the following roles.

Content Publisher

This user has access to publish content on the platform without seeking approval. This role is used to grant publishing rights to users who otherwise wouldn't have them.

They have permission to:

  • Publish pages
  • Publish blogs.

Content Creator

This user has access to create content on the platform. This role, on its own, is often used to give appropriate access to marketing and content users and third-party service suppliers that shouldn’t have access to any candidate data.

They have access to:

  • Pages and page editor - create and edit rights.
  • Blogs and blog editor.

This user role does not have access to:

  • Company and Organisation menu areas
  • Publishing rights to pages
  • Publishing rights to blogs
  • Candidate CRM & Candidate data
  • Jobs.

Content Approver

This user has the right to approve content for live publishing. This role is usually used by managers to approve content for publishing by subordinates who do not have a Content Publisher role. Users with this right get emails requesting content approval when a user without Content Publisher rights requests approval. This user may review and approve the content right from the email without needing to log in. This makes it a manager-friendly approval process.

When content is approved, it is automatically published. All content approval is logged in the User Audit Log available from the side menu, under Reports & Logs.

A Content Approver has permission to:

  • Approve content for publishing.

Recruiter

This user role has access to most functions and relevant data within the platform outside the Company and Organisation menu areas.

They can have access to:

  • Dashboard on login
  • Candidate CRM and candidate data
  • Jobs
  • Blogs
  • QR Codes.

This user role does not have access to:

  • Content menu items: Web Pages, Careers Websites, and Calls-To-Action
  • Company and Organisation menu areas
  • Reports.

Traffic Source Manager

This user can access the Traffic Sources and Traffic Source Costs pages.

Device Manager

This user has access to the Devices page.

CRM Exporter

This user can bulk export candidate data. The above roles do not grant this access.

Reporting

Users with this role will have access to the Reports section and the main dashboard.

Hosting Manager

Users with this role will have access to the Hosting and DNS section within any Recruitment Marketing companies you give them access to. The role is intended for your IT colleagues who may be assisting in the set-up of SSL certificates, DNS entries, etc.

Workflow Manager

Users with this role will be able to perform the following functions on workflows:
  • Create, edit, enable/disable, clone workflows
  • Create, edit workflow email templates.

Typically, users with the recruiter role would be granted this role if they have workflow management responsibilities.

Comments

0 comments

Article is closed for comments.