Setup gathers every administration area into one place — the people in your organisation, the roles that decide what they can do, the security that guards how they sign in, and the connections that link Pyron to the systems around it. You reach it from the main navigation, and each area has its own page below.
What you can manage
Start with the overview, then open the area you need.
- Setup — the admin home, with every management area grouped into one place.
Bring people into your organisation and decide what each of them can reach:
- Managing people — invite people, see each person's page, and remove them when they leave.
- Viewing as someone else — step into someone's view, read-only, to see exactly what they see.
- Helping with MFA — reset a locked-out person's multi-factor devices.
- Roles — create roles and choose what each one can do.
- Role members and inheritance — who holds each role, and how roles build on one another.
- Directory sharing — give a person access to a single branch of the directory.
- The access explorer — check who can see a given thing, with the evidence behind the answer.
- Policy activity — every access change, with who made it and when.
- Kiosks — shared devices staff sign in to with a PIN.
Protect how people sign in:
- Security settings — organisation-wide security controls.
- MFA methods — authenticator apps, text and email codes, passkeys and recovery codes.
- Enterprise single sign-on — sign in with your company's identity provider.
Connect Pyron to the external systems your work depends on:
- Outbound connections — connect Pyron to the external systems your automations call.
- Webhooks — notify external systems when things happen in Pyron.
- Inbound API keys — let external systems call into Pyron, safely.
- Service accounts — machine identities for integrations and automations.
Shape the AI assistant and keep its usage predictable:
- AI models — where your AI runs, and the model behind each tier.
- AI guardrails — boundaries on what the assistant can see and say.
- AI usage and budgets — keep assistant usage predictable.
Set how Pyron looks, and review what has changed:
- Branding — your organisation's colours, surface warmth and typeface.
- The audit trail — every change, who made it, and what it looked like before.
- Internal audit — the wider audit view, which also takes in support access.