HubNext
Help
Help Management

Rights and security

Rights in HubNext work in two layers. What a person can do (open a section, press a button, delete a record) is set by the role and the rights table. What a person can reach (which projects, funnels, organizations) is set by access and grants. This article covers the first layer; for the second see Project access and Roles and rights.

Where rights are set

  • Organization head and above — Management → People → the Rights button. Only your own organization changes.
  • Superadministrator — Administration → Users → Rights, any organization of your choice.

A row in the table is a function, the columns are roles: User, Manager, Head, Administrator. A switch turns the right on for the role and for all roles above it: turn it on for a manager and the manager, head and administrator have it. The last column shows the default; a changed row is highlighted, and the arrow button returns the default.

What cannot be changed

  • Superadministrator always has every right.
  • Guest, the Reports role and Operator never receive rights from this table — they are limited by the role itself.
  • Organizations are isolated: rights of one organization do not affect another, and a head cannot see or change someone else's.
  • The rights table does not open access to data: projects, funnels, guest projects and grants are configured separately and always checked. The "Delete deals" right does not give access to a deal the person cannot see.
  • Private comments, issuing roles and the Administration sections stay with the administrator and superadministrator and are not configured in the table.

Limits for a head

So that rights cannot be widened around the hierarchy, a head and an administrator change the table within their own role:

  • Only what is yours. You can change a right that is available to your role by default. Rights at the "Administrator and above" level and superadmin-only rights are not shown to you.
  • Not above your own role. A head can turn a right on for user, manager or head, but not for administrator; a right cannot be taken away from your own role either.
  • Superadmin lock. If a superadmin raised a right above your role, it is locked in your table until they return it.
  • Only your own organization. Another organization is unavailable, even through a direct request.

These limits are checked on the server, not only hidden in the interface.

Before you change something

  • Lowering a level opens the function to more people. For example, "Delete deals" for the user role lets every employee delete deals. Enable a right for a low role only if you really mean it.
  • There are no one-person exceptions. Rights are set by role: for more, raise the person's role (an administrator does this) or lower the right's level.
  • Changes apply at once, no need to log in again.
  • Every change is recorded: who, when, which right and from which level to which.

Default examples

  • Manager and above: delete leads and deals, create projects, close documents, see closed documents, change deal priority.
  • Head and above: send a task by email, delete others' contacts and quick actions in a deal, edit employees in People, configure SLA and integrations.
  • Administrator and above: edit others' task descriptions, time entries and estimates, sprints, the Meta tab, move others' tasks.
  • Superadmin only: edit the title of someone else's task.

The full list of rights and their defaults is in the table itself.