The Settings area in SpartanX is where administrators manage team members, define access control roles, monitor organization-wide usage, and configure multi-tenant workspaces. It's accessible directly at app.spartanx.ai/settings.
Organization Members
The Members tab shows all users in your organization's workspace, including:
Email address
Assigned organizational role
Workspace access level
Account status (active, pending, expired)
Expiration date (if applicable)
To invite a new user, click "Invite User," enter their email address, and assign a role. Note that the number of available seats is determined by your license — if the seat limit is reached, additional invitations won't be processed until the license is upgraded.
Roles and Permissions
SpartanX uses a role-based access control (RBAC) model. Roles range from broad administrative access to narrowly scoped read-only views:
Owner / Super Admin — full platform access, including billing and license management
Security Manager — manages engagements, vulnerabilities, and team workflows
Security Analyst / Offensive Security Specialist — full access to engagements and technical findings
Risk and Compliance Analyst — focused on compliance reporting and risk analysis
Reporting Specialist — limited to reporting functions
Read-Only Stakeholder — view-only access to results; cannot launch engagements or modify data
Role permissions are granular — for example, you may want first-line engineers to read engagement output without being able to launch new tests. The Roles and Permissions tab provides a detailed breakdown of what each role can and cannot do.
Usage Overview
The Usage section is visible to administrators and shows:
License type and included features
Percentage of credits consumed across the organization
Remaining capacity
This view is useful for capacity planning and for identifying periods of high consumption.
Workspaces and Multi-Tenancy
SpartanX supports workspaces for organizations with multiple divisions, geographies, or subsidiaries. For example, an organization with offices in the UK, Japan, and the US can split into separate workspaces — each with its own assets, engagements, and team members.
Credit allocation across workspaces can be managed in two ways:
Automatic — credits are distributed equally among workspaces
Manual — administrators set a specific credit limit per workspace, preventing any single workspace from consuming the full organizational allocation
This ensures fair resource distribution and budget control across a complex organization.
What's Next
The next section covers User Management in detail — how to invite users, understand role capabilities, and manage team access at scale.