Set organization preferences and approval rules
Set identity, timezone, branding, notification preferences, attention thresholds, and the rules that gate privileged changes.
Before you start
- Select the intended organization.
- Use an owner account to save tenant settings; other permitted roles can inspect but cannot save these changes.
Screenshots show the Rapport interface with example data. Use your organization’s devices and values. Select an image to view it at full size.
Update organization identity
Open Admin → Settings. Under Organization, edit Name and Slug, then choose that card’s Save. Save controls apply to their own section rather than committing every visible field at once. If Save is disabled, focus or hover its explanation; the console identifies the role or state preventing the change.
Set localization and branding
Under Localization, choose Default timezone and Date format, then Save. In Branding, upload a PNG or JPG logo no larger than 2 MB and choose an Accent color. After the upload succeeds, choose the Branding card’s Save to apply it; uploading alone does not apply the logo. Use the provided timezone choices rather than typing a timezone into another setting.
Choose notification preferences
Under Notifications, select Email digest as Off, Daily summary, or Weekly summary. Toggle preferences for Critical alert triggered, Agent goes offline, Integration connection failed, and New member joined, then choose Save for this section. A saved preference records desired delivery behavior; check the actual email/delivery channel when validating a notification workflow.
Configure which devices need attention
Under Dashboard thresholds, enter Low patch compliance % and Agent offline after (minutes), then save. The first flags endpoints below that compliance percentage; the second marks an endpoint stale after the no-heartbeat window. Low DEX score threshold comes from the Experience profile’s at-risk boundary. These dashboard thresholds affect attention views, not alert generation; configure alert rules separately.
Review the Experience profile
Use the Experience profile card to define the score’s zones and interpretation consistently across experience views. Review its settings and preview before saving. The at-risk zone boundary also supplies the dashboard’s low-DEX threshold, so check how the change affects the devices surfaced for attention. Use the Experience guide for the profile’s score and evidence behavior.
Choose how privileged work receives approval
Under Approvals and MFA, choose Approval by blast radius or Second admin for every privileged command. In blast-radius mode, set Device threshold and Destructive threshold; batches on more devices than the threshold require a second admin. The destructive group includes reboot, software uninstall, and agent updates. The all-privileged mode requires another admin regardless of those thresholds.
| Field or control | What to do |
|---|---|
| Machine-initiated jobs need approval | When enabled in blast-radius mode, API-key, rule, and check jobs require approval regardless of size. |
| Owners may break glass on their own requests | When enabled, an owner may approve their own request with a recorded reason; the break-glass decision is audited. |
Set MFA freshness and verify the saved policy
Choose MFA step-up window from the offered durations, then Save the Approvals and MFA section. This controls how recent the second-factor verification must be for guarded changes such as policies, API keys, approvals, and terminal sessions. Reopen or refresh the settings and verify the recorded values before relying on them in an operational run.
If something doesn’t work
Save is disabled although I am an admin.
Tenant settings are owner-editable. Ask an organization owner to save the change; administrator access does not grant this particular write permission.
The new logo has not appeared.
After successful upload, click Save in Branding. The upload success message explicitly asks you to apply it.
Changing a dashboard threshold did not create an alert.
Dashboard thresholds affect needs-attention views. Create or edit Alerts → Rules for alert generation.
A small batch still needs approval.
Check machine-initiated settings and the effective agent policy’s Always require approval for list, in addition to the tenant’s device thresholds.