Organizations and users glossary
Learn the meanings of organization and user-related terms.
Definitions of organization-related terms. Refer to the main glossary for definitions of terms across Retool.
A
Access list
A list showing which users have access to each app, folder, workflow, resource, or agent. The list shows the access level of each user
AI credit
The unit that Retool uses to track usage of AI tools in Retool. Prompts that require more complex reasoning or larger outputs use more credits.
B
Beta
This functionality is currently in active development and subject to change. Beta functionality is available for you to use but may not yet be complete.
Branding
A suite of settings that enable customers to personalize the appearance and user experience of the Retool enironement. Includes the ability to customize headers, sign up and login pages, email invites to users, the Retool user menu, and more.
Builder
Users with full access to create, edit, and deploy apps, agents, and workflows.
C
Closed beta
Functionality is available to a limited number of customers for initial testing. Retool's engineering team works directly with customers to provide access and gather feedback. For access, reach out to your account manager.
Closed beta waitlist
The waitlist that provides access to a closed beta.
Cloud
A multitenant, cloud-hosted deployment of Retool that enables companies to quickly and easily use Retool.
CORS
Cross-origin resource sharing (CORS) is a mechanism to safely bypass the same-origin policy; that is, it allows a web page to access restricted resources from a server on a domain different than the domain that served the web page.
Custom domain
A configuration option for cloud organizations that enables them to set a custom domain, which replaces retool.com in all URLs.
Custom SSO
A feature that enables organizations to integrate their own identity provider (IdP) for user authentication using industry-standard protocols—OpenID Connect (OIDC) or Security Assertion Markup Language (SAML).
D
No glossary entries found.
E
F
No glossary entries found.
G
General availability
Functionality is generally available to eligible organizations and their users.
H
No glossary entries found.
I
Invoiced customer
A customer who has a Retool account manager and is invoiced directly.
J
No glossary entries found.
K
No glossary entries found.
L
No glossary entries found.
M
No glossary entries found.
N
No glossary entries found.
O
Object role
A role that controls access to Retool objects—apps, resources, workflows, and agents. Object roles can be assigned to groups with universal access (all objects of a type) or individual access (specific objects or folders).
Organization
A distinct collection of users and data. Organizations operate separately from one another, have their own configuration settings, and are where users share access to work. If you use cloud, you have a single organization. If you self-host Retool, you have one organization per instance.
Organization role
A role that controls access to Retool administrative settings, such as SSO, billing, user management, and more. Organization roles are assigned to groups to delegate specific settings access without granting full admin privileges.
P
Permission group
A mechanism by which Retool users can be granted access to apps, agents, resources, and workflows.
Platform database
The underlying Postgres database that stores the state of the Retool application on a self-hosted instance. Stores information such as organization, user, and app data.
Public beta
This feature is currently in active development, subject to change, and may not yet be complete. The feature can be toggled on or off from the Settings > Beta page.
Q
No glossary entries found.
R
Role
A set of permissions that grant access to specific organization settings.
Role grant
The assignment of a role to a group. When a role is granted to a group, every member of that group inherits the permissions defined by that role. If a user belongs to multiple groups, their permissions are additive.
Role-based access control (RBAC)
In computer systems security, role-based access control (RBAC) or role-based security is an approach to restricting system access to authorized users, and to implementing mandatory access control (MAC) or discretionary access control (DAC).
S
SCIM 2.0 API
A commonly used API used to manage users and group membership.
Security hardening
In computer security, hardening is usually the process of securing a system by reducing its attack surface, which is larger when a system performs more functions; in principle a single-function system is more secure than a multipurpose one. Reducing available ways of attack typically includes changing default passwords, the removal of unnecessary software, unnecessary usernames or logins, and the disabling or removal of unnecessary services.
Self-serve Customer
A customer who manages their own billing and invoicing through the Retool billing platform.
Single-tenancy
A deployment model in which a single instance is provisioned exclusively for one organization, running on dedicated infrastructure not shared with any other tenant.
Space
A feature that allows you to create multiple isolated organizations within a parent organization. Each space has its own subdomain, sso confiuration, source control configuration, user accounts and permission groups, Retool Database, and data.
T
No glossary entries found.
U
User
An account that belongs or has access to an organization. Email addresses are the identifiers for users
V
Viewer
On the Business and Enterprise plans, a default permission group that cannot be modified or removed in which users have "Use" access to apps, resources, and workflows by default.
W
No glossary entries found.
X
No glossary entries found.
Y
No glossary entries found.
Z
No glossary entries found.