Summary and recommendation
Symitar 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.
Symitar (Episys) is an enterprise core banking platform built exclusively for credit unions and sold under custom contracts through Jack Henry & Associates.
Public documentation covering user management, admin console paths, permission models, or seat types does not exist - all support resources are gated behind authenticated Jack Henry client portals.
Because no verifiable workflow data is available from public sources, the steps required to add or remove users in every app connected to Symitar cannot be confirmed without direct engagement with Jack Henry.
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: Symitar 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: Symitar is sold primarily through custom or enterprise contracts. Public seat pricing and detailed licensing terms are not broadly disclosed.
The cost of manual management
Pricing for Symitar is not publicly disclosed; the platform operates on custom enterprise contracts only. No plan tiers, seat costs, or license structures are available from public sources.
Any cost assessment for manual provisioning overhead would require information obtained directly from Jack Henry account teams.
The decision
Given the complete absence of public admin documentation, teams managing Symitar access should expect to rely entirely on Jack Henry professional services or internal institutional knowledge. Standardized provisioning workflows - the kind that keep every app in sync during onboarding and offboarding - are not achievable through self-serve tooling based on currently available public information.
Direct outreach to your Jack Henry account representative is the only confirmed path to understanding what user-management automation is possible.
Bottom line
Symitar is a closed, contract-only enterprise system with no publicly accessible user-management documentation. Provisioning and deprovisioning workflows are opaque from the outside, and no self-serve admin path has been confirmed through public sources.
Any team operating Symitar should treat access management as a professional-services engagement with Jack Henry rather than a configurable admin task.
Automate Symitar 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.
