On this page

Add your team, define what they can see and do, and optionally connect Incident Tracker to Microsoft for automated user management.


Step 1 — Understand user types#

Before creating anyone, it helps to know the four common access patterns:

  • Submit only (Submit Reports) — can submit reports but cannot view existing reports
  • View own reports (My Reports Rights) — can submit and see reports they submitted
  • View reports (View Rights) — can see reports within permitted locations or categories
  • Admin (Admin Rights) — full access to configuration and report data

Visibility comes from a combination of role settings and category or location restrictions.

You will configure those in the next steps.


Step 2 — Create a new user#

Create a test user that you can sign in as during the checkpoint.

  • Set their basic account information
  • Assign their access rights
  • Apply category or location restrictions when visibility should be scoped

Step 3 — Create a user group#

User groups let you manage permissions for many users at once.

A change to the group applies to everyone in it.

This is more efficient than editing users one by one as your team grows.

  • Create a group that reflects a real role in your organization
  • Add the user from Step 2
  • Make one rights or restriction change at the group level and confirm it applies

Step 4 — Audit user access#

Two tools help you verify permissions before go-live:

  • Open Admin > Manage Users and check each user's rights and the padlock Restrictions icon. See Manage Users.
  • Export — lets you review access data in a spreadsheet for audits or deeper checks

Revisit both whenever your team structure changes significantly.


Step 5 — Explore integration options#

If your organization manages users in Microsoft Entra ID, Incident Tracker supports automated user provisioning.

This reduces manual account setup and deactivation.

  • Single Sign-On (SSO) — users sign in with Microsoft credentials. See Single Sign-on.
  • SCIM Provisioning — automatically creates, updates, and deactivates accounts. See SCIM Provisioning.
  • Microsoft Graph — an alternative provisioning method for Microsoft 365. See Microsoft Graph.
  • Google Sign-in — see Google Sign-in.


You're all set.

Your Submit Report page is configured, your workflows are running, and your users are in place.

For a deeper look at any area, continue with Getting Started or Submit a Ticket if you need help.