Skip to main content
Topic

Admin Guides

Manage user access, organization settings, and workspace configuration.

Frequently asked

Common questions about admin guides.

How does Curated bill me? What are credits?

Curated bills per seat per month, with a credit allotment per tier:

  • Starter — 2,000 credits / month
  • Professional — 10,000 credits / month
  • Professional Max — 50,000 credits / month (or unlimited with BYOA)
  • Enterprise — Negotiated allocation, fair-use

Credits are pooled at the organization level by default — heavy users and light users average out. Admins can set per-user caps and overrides at Settings → Users.

A credit represents the cost of an AI inference + spatial service call combination. Cheap operations (a simple geocode) cost a few credits; heavy operations (a multi-step site-selection playbook) cost more. Usage breakdowns live at Settings → Usage in real time — you'll see current cycle, projected burn rate, and per-agent breakdown.

What happens when I run out of credits?

Conversations pause at the org-level credit cap; in-flight prompts complete using committed credits but new prompts block until either the cycle rolls or an admin increases the allocation. Users see a clear message; admins see the cap hit in the usage dashboard.

Options to continue:

  1. Add credits — admins can purchase additional credits mid-cycle.
  2. Move tier — Professional → Professional Max raises the monthly allotment significantly.
  3. Switch to BYOA — on Professional Max, BYOA (bring your own ArcGIS keys) routes spatial-service costs to your own ArcGIS billing, removing them from Curated credits.
  4. Adjust per-user caps — if one user is consuming the pool, admins can throttle at Settings → Users → Credit override.

Credits don't roll over between cycles. Cycle anniversaries are configurable per organization.

How do I invite team members?

Admins manage org access at Settings → Users:

  1. Click Invite user.
  2. Enter email + role (Admin, Analyst, Viewer).
  3. The user receives an email with a sign-in link scoped to your tenant.

If your org has a claimed domain (e.g., acme.com), users signing up with a work email at that domain land directly in your workspace — no manual invite required. You can configure this at Settings → Authentication → Workspace access.

Roles:

  • Admin — full org control, billing, user management, settings.
  • Analyst — full access to Spaces, conversations, and artifacts; cannot modify org settings or billing.
  • Viewer — read-only access to artifacts and shared maps. Counts as a Viewer seat on tiers that include them (Professional includes up to 10).
Can Curated be embedded inside our existing tools?

Two embedding paths today:

  1. Curated Widget — drop a JS snippet into any site or internal portal to embed the chat-and-map surface. Per-widget configuration (theme, scope, capabilities). Available from Professional Max.
  2. Curated Connector for ArcGIS Experience Builder — drop the connector into any ExB app and your users get conversational analysis over the web map they're already using. No separate URL, no context switch. Available from Professional Max.

White-label / OEM private-label deployments — where Curated runs under your brand entirely — are scoped per partner contract. Talk to sales for licensing and operating-model details.

Does Curated support SSO and SCIM?

ArcGIS Identity sign-in is available from Professional — your team signs in via ArcGIS Online identity, with token refresh and audit trail. Social auth (Google, Microsoft, GitHub, Salesforce) is available on all tiers.

Provider SSO (SAML 2.0 / OIDC against Okta, Entra, Google Workspace, or any IdP) plus SCIM 2.0 provisioning is scoped on the Enterprise tier — talk to sales for inclusion in an enterprise engagement.

Workspace-access controls at Settings → Authentication govern who can self-join via your claimed email domain.

Where is our data stored, and can we control the region?

Default Curated deployments are multi-tenant SaaS hosted in the United States with schema-level isolation per customer.

For organizations with regional residency requirements:

  • Customer VPC — Curated deployed inside your AWS, Azure, or GCP account. Your data stays in your perimeter. Scoped per Enterprise contract.
  • Single-tenant cloud — Curated-hosted but on dedicated infrastructure for your organization, with regional residency options. Scoped per Enterprise contract.
  • Bespoke / regulated deployments — for gov, defense, healthcare, and adjacent regulated workloads, architecture is scoped per engagement.

All deployment options inherit the SOC 2 Type II and HIPAA-compliant operating environment Curated is built within.

Where can I see my usage and credit consumption?

Per-user view: top bar of the workspace shows your remaining credits in real time.

Admin view: Settings → Usage shows the organization's current cycle, projected burn rate, per-agent breakdown, and per-user roll-ups. Drill into any user to see their last 100 prompts and what each cost.

Pending credits (committed to in-flight conversations) display separately from settled spend so the numbers reconcile cleanly.

Cycle anniversaries are configurable per organization at Settings → Billing.