Summary and recommendation
SS&C Advent Geneva user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
SS&C Advent Geneva is an enterprise-only portfolio accounting platform sold exclusively under custom contracts.
There is no self-service admin console path or publicly documented user management interface available outside of SS&C's authenticated client portal.
Because all administration documentation is gated, independent verification of provisioning workflows is not possible.
Unlike every app that supports a public admin UI, Geneva routes all access changes through vendor-mediated engagement.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| SCIM available | No |
| SCIM tier required | N/A |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Can manage tenant settings, integrations, and user access. | Cannot grant capabilities outside the modules or features enabled for the tenant. | Detailed built-in role names are not fully documented publicly. | ||
| Standard User | Can use the core product features exposed to their assigned role. | May not be able to manage tenant settings, integrations, or other users. | Exact privileges can vary by tenant configuration and contract scope. |
Permission model
- Model type: role-based
- Description: SS&C Advent Geneva appears to use role-based access for tenant administration and general product use, but the detailed permission matrix is not publicly documented in full.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Expect administrative access to be separated from standard user access, with exact scopes configured per tenant.
How to add users
- Log in as an administrator.
- Open settings or administration and navigate to users.
- Choose the add or invite user action.
- Enter the user's work email and assign the appropriate role.
- Save the user and complete any activation or SSO steps required by the tenant.
Required fields: Work email address, Role
Watch out for:
- Public documentation for user administration is limited, so exact labels may vary by tenant.
- If SSO is enabled, upstream IdP assignment may still be required before the user can sign in.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | Unknown | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Public docs do not clearly document whether users are disabled, deleted, or both. Treat lifecycle behavior as tenant-specific unless confirmed in-product.
- Open the users area as an administrator.
- Locate the user to offboard.
- Disable, revoke, or remove the account using the controls available in that tenant.
- Review any integrations, service accounts, or credentials associated with the departing user.
| Data impact | Behavior |
|---|---|
| Owned records | Tenant data remains in the workspace; public docs do not describe user-owned content semantics in detail. |
| Shared content | Shared content and workspace records typically remain available unless separately removed or reassigned. |
| Integrations | Review service credentials, workflow ownership, and integrations separately during admin offboarding. |
| License freed | Seat reuse behavior is contract-dependent and not publicly documented in detail. |
Watch out for:
- Offboarding should include token, integration, and service-account review, not just interactive login removal.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Named User | Access to the tenant features exposed to the assigned role. Seat entitlements are generally tied to the subscription contract. | Custom pricing; determined by contract and plan. |
- Where to check usage: Settings / Administration > Users and Roles
- How to identify unused seats: Review the tenant user list and any visible login or activity metadata. No public unused-seat report was verified.
- Billing notes: Geneva is an enterprise-only platform sold under custom contracts. Pricing and seat licensing details are not publicly disclosed.
The cost of manual management
Without a public admin console or self-service provisioning interface, every app lifecycle action - adding a user, adjusting permissions, or offboarding a departing employee - requires direct engagement with SS&C Advent client services or professional services teams. This creates a hard dependency on vendor response times for routine access changes.
At scale, that dependency compounds: coordination overhead falls on IT or operations staff for every change request.
The decision
Geneva is purpose-built for institutional investment operations and is not designed for self-service IT administration. Unlike every app that exposes a standard provisioning interface, Geneva requires a vendor-mediated access model from the outset. Seat licensing and pricing details are not publicly disclosed;
all commercial and access terms are negotiated directly with SS&C.
Bottom line
SS&C Advent Geneva operates as a fully managed, enterprise-only platform where user provisioning and access management run through SS&C client services - not through a self-service console or public API.
Documentation is client-gated, public community data is effectively absent, and every access change requires vendor coordination. Organizations with strict joiner-mover-leaver SLAs should factor that dependency into their access governance planning before deployment.
Automate SS&C Advent Geneva workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
