Auroranexis

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.

Overview

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.

Purpose

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.

Core Concepts

Workspace and organization

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.

Roles and permissions

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	Read-focused access for review, finance oversight, and portfolio reporting without edit rights.

Features

Self-service sign up with email and password; password reset via the login page.
Operations Command Center dashboard with portfolio signals and quick links.
Settings hub for organization, team, billing, usage, SLA, escalation, branding, and email.
Role-based access control with owner, admin, staff, and viewer roles.
Clients module for portfolio management, health scores, owners, and portal user administration.
Reports with templates, schedules, draft and publish workflow, PDF export, and portal delivery.
Risks and Incidents with ownership, SLA timers, and optional portal visibility on incidents.
Monitoring connectors linked to clients with event history and health impact.
Stripe checkout, invoices, and customer portal for subscription management.
Usage meters for clients, monitoring connectors, and plan-specific limits.
Activity logging across major operational records for audit-friendly history.
Client portal publishing for reports and selective incident transparency.

Step-by-step usage

Go to Sign up, enter your name, agency name, email, and password, then confirm your account.
Sign in to reach the Operations Command Center dashboard.
Open Settings → Organization and verify your workspace name and profile details.
Open Settings → Team and invite owners, admins, staff, or viewers as needed.
Review Settings → Billing to confirm your plan; complete Stripe checkout if upgrading.
Check Settings → Usage to understand current limits before adding many clients or connectors.
Add your first client from Clients → New client with status and internal owner assigned.
Open Settings → SLA and create or review policies before assigning them to clients.
Create a report template under Reports → Templates, then generate a draft report for the client.
Review the draft internally, publish when ready, and add portal users on the client detail page.
Optionally configure Settings → Escalation rules for SLA warning and breach notifications.
Schedule a weekly operations review using dashboard metrics and client health scores.

Best Practices

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.

Maintain at least two owners on active workspaces for continuity during leave or turnover.
Assign one primary internal owner per client to keep accountability clear.
Review Settings → Usage before onboarding large client batches to avoid hitting plan limits.
Use consistent naming for clients and report templates across your portfolio.
Document significant risks and incidents early rather than relying on informal channels.
Enable the client portal only after internal review of published content.
Align SLA policy names with contract language before assigning policies at scale.
Designate an operations lead responsible for weekly health review and reporting cadence.
Configure branding and email defaults in Settings before inviting external portal users.
Export or archive critical reports before any planned subscription cancellation.

Examples

Marketing agency

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.

AI automation agency

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.

MSP

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.

Consultancy

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.

Enterprise deployment

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.

Troubleshooting

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.

FAQ

Who should be the workspace owner?: Assign owners to people who manage billing, team access, and contractual decisions. Most agencies designate a founder or operations director plus a backup owner.
Can I change my workspace name later?: Yes. Owners and admins can update organization details in Settings → Organization. Client-facing branding is configured separately in Settings → Branding.
Do clients need their own Auroranexis accounts?: No. Internal team members use the main application. Client contacts receive portal user accounts scoped to a single client and sign in through the client portal.
What happens when I hit a plan limit?: Creation actions such as adding clients or monitoring connectors may be blocked. Review Settings → Usage for current consumption and upgrade in Settings → Billing if needed.
Is there a recommended order for first modules?: Configure team and billing first, then clients and SLA policies, then reports and portal access. Add monitoring once baseline delivery is stable.
Can staff manage billing?: Billing changes require owner or admin roles with billing permissions. Staff can review operational data but cannot modify subscriptions or payment methods.

Clients, plans, and portal users

Client — a customer account your agency manages; links reports, risks, incidents, monitoring, and portal access.
Plan — subscription tier that controls feature availability and usage limits enforced in Settings → Usage.
Client portal — separate sign-in for external contacts, scoped to one client and its published content.
SLA policy — organization template assigned per client; drives incident and risk timers.

Settings hub

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.