Organization Settings

The Settings page is your organization's control center. Most operational configuration lives here, organized into clear sections.

General

Organization identity and branding.

• Organization name — the human label shown in the sidebar and to invitees.
• Slug — used in URLs and (when you make agents public) in shareable links.
• Website — optional, used in invite emails and the public agent profile.
• Logo — optional, surfaces in participant-channel messages and invitation flows.

Profile

Per-user (not per-organization).

• Name and avatar
• Email address (Fruxon has no passwords; see Sign-in & SSO)
• Notification preferences

Team Management

Invite, role-manage, and remove members. Full coverage in Team & Roles.

Working hours

Settings → Working hours defines when your human team is at work: named weekly schedules in one IANA time zone, with per-day time ranges (overnight shifts allowed), dated exceptions for holidays and short days, and an optional closing-soon window. They're workspace-wide, so one schedule can serve several Applications. Attach one under an Application's People → Escalation → When the team is working, and its agents are told each turn whether the team is working, so they don't promise a teammate who's off. See Working hours.

Sign-in and access

How people get into the workspace, and the record of what they did there. Domains sits in the Workspace group; the rest are in the Security group.

• Domains — prove your company owns a domain by publishing a DNS TXT record. Available on every plan; single sign-on builds on it. See Sign-in & SSO → Domains.
• Sign-in methods — choose which ways of signing in (Google, Microsoft, GitHub, email code, single sign-on) can reach the workspace. API tokens aren't affected. Available on every plan. See Sign-in & SSO → Sign-in methods.
• Single sign-on — connect a SAML 2.0 identity provider such as Okta or Microsoft Entra ID, attach your verified domains, and choose whether people can join without an invitation. Enterprise plan. See Sign-in & SSO → Single sign-on.
• Audit log (Enterprise) — who did what in the workspace, including changes, reads of personal data, and Fruxon staff access, with filters and CSV/NDJSON export for Owners and Admins. See Audit Log.

Sensitive changes, such as minting a token, changing a member's role, sign-in methods, single sign-on, data retention, or encryption keys, ask you to confirm it's you if you signed in more than 15 minutes ago.

API access

Organization-scoped, scoped access tokens for server-to-server access — split into personal access tokens (fx_pat_…, authenticate as you) and service-account tokens (fx_sat_…, authenticate as a workload identity). Mint with a preset (Observer, Operator, Developer, Maintainer, Admin) or hand-pick scopes; personal tokens always expire, after at most a year; rotate with optional scope/expiry overrides; every issuance and rotation is audited. Tokens are sent in the Authorization: Bearer header.

Quick start:

1. Settings → Personal access tokens → Generate token.
2. Pick a preset (or scopes), name it (prod-server, ci-evals, support-zendesk-bot), and choose an expiry — up to 1 year, which is the default.
3. Copy the secret — it's shown once.

curl -X POST "https://api.fruxon.com/v1/tenants/{tenant}/agents/{agent}:execute" \
  -H "Authorization: Bearer $FRUXON_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"parameters": {"topic": "the EU AI Act"}}'

See the Tokens guide for the full scope vocabulary, rotation semantics, audit history, MCP auto-mint, and the inbound:deliver flow for webhooks and Agent Network inbound routes.

Usage

What your workspace is consuming this billing cycle, led by Credits used: run credits used against your plan's allowance, what's left, a forecast for the cycle, and history by source and by agent. See Run credits.

Use Usage to spot the agent that's eating your allowance before it runs out.

Billing

Plan, payment method, invoices. Admins can:

• Upgrade or downgrade
• Update card / billing email
• Download invoices
• Buy Top-up credits, set a low-balance alert, or turn on automatic top-ups

Model Pricing

The per-model token rates Fruxon uses to compute cost, marked Default or Override. Click Edit pricing to enter your negotiated rates, optionally from an Effective from date; Reset to default removes the override. See Custom pricing.

Evaluation Metrics

Define the rubrics your evaluations score against. See Evaluations.

Next steps

• Team & Roles — manage members
• Security — audit, secrets, compliance
• Sign-in & SSO and Audit Log — how people get in, and what they did
• Cost & Budgets — keep spend in check at the agent level
• API Reference — call the API with your keys