Accounts
An account is a tenant that logically separates the information and configuration of different areas or organizations within Gredit. Each account functions as an independent environment with its own database schema, users, scripts, jobs, cases, and other resources.
What it is used for
Separating the business logic of different areas of an organization through multi-tenancy. It allows multiple departments, subsidiaries, or clients to operate on the same Gredit instance with completely isolated data.
Configuration
| Field | Description |
|---|---|
| Account name | Descriptive name of the account |
| Context (tenant) | Unique tenant identifier (read-only once created) |
| Style | Visual appearance of the account |
| Token duration interval | Session token lifetime |
| Token duration frequency | Token time unit |
| Delete runs after | Days after which runs are deleted |
| Delete executions after | Days after which executions are deleted |
| Records per page | Number of records per page in listings |
| Group scripts by job | Group the scripts view by job |
Security
warning
- The tenant name is read-only once created.
- Data is completely isolated between accounts.
- Only users with appropriate permissions can access each account.
Relationship with other modules
- Users: Users can have memberships in multiple accounts
- Databases: Each account can have its own configured connections
- Drives: Each account can have its own storage services
- Integrations: Each account can have its own external integrations
- LDAP/SAML: Authentication configuration can vary by account
- All resources: Scripts, jobs, rules, cases, etc., belong to a specific account and are isolated