Skip to main content

All Gravy Permissions and what they mean

Permission is set per person from the People directory. The four you can pick are Admin, Editor, Manager and Employee. Five more exist, and permissions are not the same thing as roles.

In All Gravy, access is controlled by:

  1. Permission (per person)

    • Set from the People directory under “Edit permissions”.

    • Four options: Admin, Editor, Manager, Employee.

    • Defines access across modules like Insights, Pulse, Surveys, Reports, Handbooks, Academy, Feed, To-do lists, Chats, People Directory and Settings

Before you read on: permission is not the same thing as a role. A role under Directory is a job-title tag used for filtering and for targeting content, and it grants nobody any access at all. If someone cannot do something, their permission is the thing to change, never their role.

Admin

Who it’s for: HR/Leaders

What it means:

  • Full access to all modules (Insights, Pulse, Surveys, Reports, Handbooks, Academy, Feed, To-dos, Chats, People Directory, Settings), depending on what your org has activated.

  • Can manage the organisation setup: locations, areas, districts, integrations, and general settings.

  • Can invite / remove users and change their roles and permission packages.

  • Can see insights and reports across the whole organisation where the package allows (engagement, usage, surveys, etc.).

Only an account admin can edit roles for other users.

Editor

Who it’s for: People who build and maintain content, but don’t need full account control.

What it typically means (high level):

  • Can create and update content in modules like Handbooks, Academy, Feed, To-do lists, Surveys, depending on the permission package.

  • Usually cannot change core organisation settings – that’s reserved for Admins.

You can think of Editor as:

“I run the show content-wise, but I don’t re-wire the system.”

Manager

Who it’s for: Local leaders – e.g. restaurant managers, store managers, shift leaders.

What it means:

  • Same app experience as employees, plus extra rights tied to their locations.

  • The Manager role is always scoped to an “Area” , so they only see and act on what’s relevant to their locations.

  • Typically can:

    • View local insights / reports for their stores (retention, engagement, usage) where the package allows.

    • Send targeted feed posts, messages, and tasks to their teams.

    • Manage some local operational content (e.g. to-do lists for their location).

Managers are your frontline band leaders – strong control in their “section”, but not across the full orchestra.

Employee

Who it’s for: All regular team members using the app.

What it means:

  • Uses the app to:

    • Read feed posts & chat with colleagues.

    • Access handbooks, training (Academy), to-dos, surveys, whistleblower, etc.

  • Cannot:

    • Change organisation settings

    • Create and Edit articles

    • Create Events and Broadcast

    • Create To do Lists

    • Add new users

    • Manage other users

    • Access admin-level insights or permission settings

Employees are the audience and performers, not the sound engineers.

Other permissions you may come across

The four above are what you choose from in “Edit permissions”. All Gravy has five further permission types, which you may see referenced in other articles or in a reply from us:

  • Super Admin — All Gravy's own support access. It is not something a customer account can grant

  • Creator — builds content and can also reverse a deactivated employee

  • Content Creator — content only, narrower than Creator

  • Staff Manager — manages people, including reactivating a deactivated employee

  • HR

Two of these cannot be granted by an account admin. If you try to give somebody Super Admin or HR, the change is dropped without an error message. If you need one of them, chat with us rather than trying again.

This is also why reactivating a deactivated employee is not Admin-only: Admin, Creator, Super Admin and Staff Manager can all do it.

In Summary:

  1. AdminFull control of All Gravy. Can manage users, locations, settings and integrations, and access all available modules and insights across the organisation.

  2. EditorContent and communication owner. Can create and manage content like handbooks, training, feed posts, surveys and to-do lists, but doesn’t control core account settings.

  3. ManagerLocal leader. Has extra rights for their assigned locations (area/district), such as viewing local insights and sending content to their team, but not full account-wide admin access.

  4. EmployeeEnd user. Uses the app to read updates, chat, complete training and tasks, and respond to surveys, with no admin or configuration rights.

Did this answer your question?