Skip to main content
ASIRI

Manage tenant settings without technical fields

Use guided settings for company profile, branding, Trust Center, notifications, security, API keys, webhooks, and billing.

Help center
Workspace administration7 min readUpdated May 2026Settings
Access needed
OwnerAdmin
ASIRI tenant settings page with guided sections
Settings should be understandable for non-technical operators. Use plain labels, dropdowns, helper text, and previews instead of raw JSON.
ASIRI Branding settings page with guided brand identity and live preview
Branding settings use plain fields, color pickers, upload controls, and previews instead of raw configuration.
ASIRI Trust Center settings page with guided publication controls
Trust Center settings separate public-facing content, gated resources, custom domains, and disclosures into guided sections.
ASIRI webhooks settings page
Technical settings such as webhooks and API keys should still explain purpose, scope, status, and risk in plain language.

Use the settings areas

Settings is organized by the kind of decision the user is making: company profile, branding, members, security, Trust Center, notifications, API keys, webhooks, billing, and rate limits.

Non-technical users should not need to read raw JSON to complete standard tenant administration.

When to involve a technical owner

Use a technical owner for SSO, API keys, webhooks, connector credentials, DNS, custom Trust Center domains, and security headers. Keep business-facing settings readable for DPOs, operators, legal teams, and founders.