> For the complete documentation index, see [llms.txt](https://docs.incident-tracker.com/llms.txt). Every page is available as Markdown by appending `.md` to its URL.

# Part 3 — Users, Permissions & Integrations

Add users, verify permissions, and connect Microsoft identity tools.

Source: https://docs.incident-tracker.com/admin-guide/setup-walkthrough/part-3-users-permissions-and-integrations  
Last updated: 2026-07-01

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

> **Note**
>
> Complete [Part 1 — Customize Your Submit Report Page](https://docs.incident-tracker.com/admin-guide/setup-walkthrough/part-1-customize-your-submit-report-page) and [Part 2 — Notifications, Workflows & System Settings](https://docs.incident-tracker.com/admin-guide/setup-walkthrough/part-2-notifications-workflows-and-system-settings) before starting here. User restrictions reference the categories and locations configured in Part 1.

---

## 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

> **Note**
>
> See [Create New User](https://docs.incident-tracker.com/admin-guide/users/create-new-user) for full setup instructions.

---

## 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

> **Note**
>
> See [Manage User Groups](https://docs.incident-tracker.com/admin-guide/users/manage-user-groups) for full setup instructions.

---

## 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](https://docs.incident-tracker.com/admin-guide/users/manage-users#user-rights-and-permissions).
* **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](https://docs.incident-tracker.com/admin-guide/application-information/authentication-settings/single-sign-on).
* **SCIM Provisioning** — automatically creates, updates, and deactivates accounts. See [SCIM Provisioning](https://docs.incident-tracker.com/admin-guide/application-information/authentication-settings/account-provisioning/scim).
* **Microsoft Graph** — an alternative provisioning method for Microsoft 365. See [Microsoft Graph](https://docs.incident-tracker.com/admin-guide/application-information/authentication-settings/account-provisioning/microsoft-graph).
* **Google Sign-in** — see [Google Sign-in](https://docs.incident-tracker.com/admin-guide/application-information/authentication-settings/google-sign-in).

> **Warning**
>
> SCIM Provisioning and Microsoft Graph require an Enterprise subscription.

---

> **Tip**
>
> **Checkpoint:** Sign in as the non-admin user you created in Step 2. Submit a test report and verify their report visibility matches the rights you assigned. This is the best way to confirm your permission setup before rollout.

---

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](https://docs.incident-tracker.com/admin-guide/getting-started) or [Submit a Ticket](https://docs.incident-tracker.com/support/need-help/submit-a-ticket) if you need help.
