Product / Knowledge Base / 9. Settings, Roles, and Groups

9. Settings, Roles, and Groups

User & Administration Guide — Version 1.0.0.24

Guide summary

Settings is limited to app administrators. Site owners are added during setup.

On this page

Security page

Settings Security with administrators, roles, assignments, and SharePoint groups
Settings, then Security.

App administrators can open Settings. Site owners are added to that list when setup runs.

  • App Administrators — who can open Settings.
  • Roles and Permission Matrix — feature flags for view, edit, setup, and reports.
  • User Assignments — a person or a SharePoint group mapped to a role.
  • SharePoint Groups — four site groups created for the default roles.

SharePoint groups

Procurement Hub modules for requests, portfolio, and administration
Requests, the portfolio, and administration share the same SharePoint lists.

Permissions in the app are enforced in the interface. SharePoint list permissions are not replaced.

SharePoint groupRole
Procurement Hub Organization AdminsOrganization Admin
Procurement Hub ManagersProcurement Manager
Procurement Hub BuyersBuyer
Procurement Hub ViewersViewer

Membership in a group grants that role. If someone is in more than one group, the higher role wins. The app reads the signed-in user's SharePoint groups and picks the highest matching role.

Four layers

  • SharePoint. Site visitors, members, and owners still control who can open the page and read the lists.
  • App administrators. The Administrators list is required for Settings and setup.
  • Application roles. Role definitions and the permission matrix live in the site.
  • SharePoint groups. Setup creates them and maps them to the default roles.

Form templates

Form templates that add fields by category
Form templates attach extra fields by category.

A template linked to a category adds those fields when someone creates or edits a request in that category.

Phases and statuses

Request phases and statuses in Settings
Request phases and statuses are configured here.

Keep the phase order aligned with the lifecycle. Requests advance one phase at a time.