Skip to main content

Policies and auto-approval

Policies decide what happens to an integration or sharing request before a person sees it. Routine, low-risk requests are approved instantly; anything outside what IT allows is refused with the reason; everything else goes to an approver.

Order of evaluation​

  1. Max scopes. If any requested scope is outside the integration's max scopes (Admin › Integrations), the request is refused, naming the scopes and the limit.
  2. "Require the requester's manager" rules. If one matches, the request goes to approvers and the requester's manager. These rules win over auto-approval.
  3. Auto-approve rules. If one matches, a grant is created at once (audited as grant.auto).
  4. Otherwise a request goes to the integration's approvers (plus the requester's manager when the request is to show file data to the app audience).

Built-in rules​

RuleEffectOn by default
Graph read of the user's own files: autoAuto-approve Microsoft 365 user:read, files:read, lists:read as the user✓
Salesforce read for Sales: autoAuto-approve read-only Salesforce for the Sales department✓
Share within own department: autoAuto-approve sharing an app within the owner's department (only matters when the manager rule below is on)✓
Teams messages to people who can open the app: autoAuto-approve Teams recipients who can all already open the app✓
Mail from an app to its owner: autoAuto-approve Microsoft 365 mail.send:owner as the project✓
Sharing beyond the owner's department needs their managerWidening app access past the owner's department waits for the manager

Built-in rules can be edited or turned off, but not deleted.

Add or edit a rule​

  1. Open Admin › Policies (Org Admins; Auditors read only).
  2. Select an existing rule, or add one under Auto-approve rules.
  3. Fill in the form:
FieldMeaning
NameShown on requests and in the audit log
EffectAuto-approve, or Require the requester's manager
KindIntegration access, Show data to the app audience, or Sharing the app
IntegrationOne integration, or any
Runs asThe user, The project, or any
AccessRead (the request must be read-only), Write (must include a write), or any
Scopes (all must match; * wildcards)Every requested scope must be covered, e.g. files:read, user:read
Requester departmentse.g. Sales, Finance
Requester groupse.g. Support Leads (names or ids)
AudienceWithin the owner's department, People who can open the app, or Only the project owner
  1. Save. The console shows a plain-English summary of each rule, for example "salesforce · read-only · requester in Sales → auto-approve".

You can also edit the raw Match (JSON):

{
"integration": "salesforce",
"access": "read",
"departments": ["Sales"]
}

Integration settings that act as policy​

For each integration in Admin › Integrations:

SettingEffect
EnabledTurned off, every call answers INTEGRATION_DISABLED (existing grants are kept)
Max scopesThe hard ceiling; requests outside it are refused
ApproversWho reviews requests (users or groups). With none, Org Admins decide.
Data sensitivityLow, medium or high; shown on every request
tip

Start strict: turn off auto-approve rules you're unsure about and watch the Requests inbox for a few weeks. Add rules for the requests you approve every time.

Availability

Guest policies, runtime limits and expiry defaults in Admin › Policies are in the design but not built yet. Project expiry is set on Admin › Roles; see Project lifecycle.

Was this page helpful?