Neobora
Book a demoTry for free
Learn Neobora/Management (web)/User permissions and roles
Basicper vertical

User permissions and roles

Updated Apr 2026·5 min read

Control who accesses each project and what they can do. Permissions are granular: by project and by role. The mechanics are common to all profiles; at the end you’ll find examples by vertical.

Owner and permissions

The Owner is whoever creates the project: they always have full permissions and cannot be edited or removed. For everyone else, you grant permissions granularly — turning on only the ones they need:

  • Project team admin — manages the team and the project’s permissions.
  • Editor — edits the project’s data.
  • Manage maps (Map manager) — creates and organizes maps.
  • Remove maps — deletes maps.
  • Manage layers (Layer manager) — manages layers.
  • Remove layers — deletes layers.
i
Note. With no permissions enabled, the invited person has read-only access.

Invite and assign permissions

  1. 1Open the project and go to the Permissions tab.
  2. 2Click Invite and enter the person’s email.
  3. 3Turn on the permissions you want to grant them.
  4. 4Click Save Changes.
i
Note. Permissions are per project: the same person can be an admin in one project and read-only in another.

Working with subcontractors

Grant edit access to a subcontractor only for the project that applies to them, keeping full control of the data without exposing the rest of your portfolio. When finished, revoke access with one click.

How it’s used in each vertical

Example for:
Permissions at a network operator

The central GIS team administers; O&M technicians in each area access with read to their corridor’s internal geoportal. The flight company uploads data with temporary edit access.

  • Zone-based access: each branch sees only its section of the network.
  • Critical infrastructure data: review the activity log every quarter.
Was this article helpful?
We use our own cookies, necessary for the site to work, and, if you accept them, external services (reCAPTCHA and the subscription and contact forms) that involve loading third-party resources. You can accept them, reject them, or read more in our cookie policy.