The Settings area in SpartanX allows organizations to manage personal profile details, define storage behavior, and control who can do what inside the platform. For teams deploying SpartanX across multiple stakeholders, this area is essential for safe and practical administration.
Manage profile details
The profile area is where users can update their display name, profile picture, and other personal account information. This helps keep the platform organized and makes ownership and collaboration clearer across the team.
Choose where data is stored
By default, SpartanX stores uploaded files internally. If your organization prefers to keep files in an external system, you can connect a storage provider such as Google Drive and route uploads, reports, and imports there instead.
This can be useful when an organization has a preferred storage policy or wants documentation and evidence to live in an existing shared repository.
Use role-based access control
User management in SpartanX is built around clearly defined roles so that access is matched to responsibility. This is particularly important in offensive security workflows, where launching an engagement against the wrong environment could create unnecessary risk.
Role | Access level | Intended use |
Security Manager | Highest | Full administrative access across the platform |
Offensive Security Specialist | High | Red teamers and penetration testers who run engagements and work with findings |
Security Analyst | Medium-High | Analysts who review findings and engagement data |
Risk and Compliance Analyst | Medium | Users focused on governance and regulatory reporting |
Reporting Specialist | Limited | Users who only need reporting functionality |
Read-Only Stakeholder | Lowest | Executives or external parties who only need visibility |
Why role assignment matters
Good access control protects both the organization and the workflow. Junior users should not be able to trigger high-impact actions without approval, while the teams responsible for testing and remediation still need enough access to do their jobs efficiently.
The goal is to assign each user the minimum level of access required for their work, while preserving clear oversight for higher-risk actions.
Recommended setup approach
When onboarding a team, begin by defining roles before broad rollout. Confirm who needs to launch engagements, who only needs to review findings, and who only needs read access. Then review storage preferences so your reporting and evidence files are aligned with internal policy from the start.
A careful setup in the Settings area makes the rest of the SpartanX deployment smoother, safer, and easier to govern.