Loading workspace...
Auroranexis documentation
Auroranexis is an operations platform built for agencies that manage multiple clients. After you create an account, your team works inside an organization-scoped workspace where clients, reports, risks, incidents, monitoring, and billing are kept together. This guide covers account creation, role assignment, and the first operational steps that establish a reliable delivery baseline for your agency.
Getting started in Auroranexis means creating your agency workspace, inviting teammates with appropriate roles, and configuring the settings that govern delivery. The Operations Command Center dashboard surfaces portfolio health, open incidents, SLA status, and recent activity so operators can orient quickly without hunting across disconnected tools.
Your workspace is an isolated tenant. All modules—Clients, Reports, Risks, Incidents, Monitoring—read and write data only within your organization identifier. Internal users, portal users, and automation workflows all respect this boundary, which keeps client data segregated and audit-friendly as your portfolio grows.
Billing runs through Stripe. Plan limits on clients, monitoring connectors, and advanced modules are enforced at the organization level. Owners and admins manage subscriptions in Settings → Billing; all roles can review effective limits in Settings → Usage before onboarding large client batches.
The recommended onboarding path moves from workspace identity and team access to your first managed clients, then to SLA policies, report templates, and optional portal access. Completing these steps in order reduces rework and ensures health scores, SLA timers, and portfolio views reflect accurate data from day one.
The onboarding path is designed to move an agency from empty workspace to operational readiness without custom setup. You establish who can access what, add your first managed clients, and connect delivery artifacts—reports, SLA policies, monitoring—to those clients so daily operations have a single system of record.
Early configuration reduces rework later. Assigning owners, aligning SLA policies with contracts, and defining report templates before bulk client import keeps portfolio data consistent. Teams that skip these steps often discover mismatched SLA timers, incomplete health scores, or portal users added before published content exists.
For agency leadership, a well-configured workspace supports weekly operations reviews, quarterly business reviews, and escalation decisions without exporting data to spreadsheets. The goal is not merely to sign up—it is to reach a state where every client has an owner, a policy, and a reporting cadence your team can defend in client conversations.
Contact support@auroranexis.com for onboarding support, billing questions, or product guidance. Include your workspace name, the module you are working in, and a brief description of your goal so we can respond efficiently.
Your workspace is an isolated tenant identified by your organization profile. Settings → Organization holds the workspace name and profile details that appear in internal navigation. All operational records—clients, reports, risks, incidents, monitoring connectors—inherit this scope automatically.
Users invited to your workspace cannot access data from other organizations. If someone participates in multiple agencies, they receive separate invitations and sign in to the workspace they need. This model mirrors how agencies serve distinct client portfolios without commingling data.
Internal role summary
| Role | Description |
|---|---|
| Owner | Full workspace control including billing, team management, and all operational modules. |
| Admin | Manage operations and most settings; billing access depends on assigned permissions. |
| Staff | Day-to-day create and update access on assigned modules such as clients, reports, and incidents. |
| Viewer |
Treat onboarding as a one-week sprint: day one for workspace and team, days two and three for clients and SLA, days four and five for templates and first published report. Agencies that follow this rhythm reach defensible portfolio visibility faster than those who add clients before policies exist.
A fifteen-person marketing agency signs up on Professional, invites two admins and six staff users, and adds twelve active clients with account managers as owners. They create a monthly operations report template, assign Standard SLA policies matching their MSA, and enable portal access for three strategic accounts after the first published report cycle.
An automation consultancy on Professional configures five clients who receive workflow monitoring via HTTP connectors linked on each client record. They log Medium incidents when integrations fail, publish quarterly executive summaries, and upgrade through Settings → Billing when client count approaches plan limits.
A managed services provider imports twenty clients in batches while watching Settings → Usage, defines Premium and Standard SLA tiers in Settings → SLA, and pairs escalation rules for critical accounts. Monitoring connectors feed events that staff triage into incidents during daily standups.
A strategy consultancy with a small delivery team uses viewer roles for partner reviewers, maintains Watch status on at-risk engagements, and publishes post-engagement reports through the client portal. Risks capture scope and resource constraints before they become client-impacting incidents.
A large agency workspace designates multiple owners, segments staff by client portfolio using ownership assignments, and standardizes report templates across business units. They configure Settings → Escalation for breach notifications and review compliance metrics in the Operations Command Center before executive QBRs.
Common getting-started issues
| Problem | Cause | Solution |
|---|---|---|
| Cannot sign in after registration | Incorrect password or unverified email | Use Forgot password on the login page; confirm the correct email with your workspace admin. |
| Missing menu items or modules | Role or plan does not include that feature | Ask an owner or admin to verify permissions in Settings → Team and subscription in Settings → Billing. |
| Invitation email not received | Spam filtering or incorrect address | Check spam folders; confirm the address in Settings → Team and resend the invitation. |
| Checkout completed but plan unchanged | Stripe webhook delay or session mismatch | Refresh Settings → Billing; contact support with the approximate checkout time if the issue persists. |
| Read-focused access for review, finance oversight, and portfolio reporting without edit rights. |
Settings centralizes organization profile, team, billing, usage, SLA policies, escalation rules, branding, and email defaults. Most onboarding tasks route through Settings before you work in operational modules. Owners and admins configure policies; staff consume them when logging incidents or publishing reports.
| Cannot add new clients |
| Client limit reached on current plan |
| Review client limits in Settings → Usage or upgrade via Settings → Billing. |
| SLA timers not visible on incidents | No policy assigned to the client | Assign an SLA policy on the client detail page or create one in Settings → SLA first. |
| Portal user cannot access published report | Report not published or user disabled | Confirm report status is Published and portal users are active on the client detail page. |
