Fabricate account structure
Last updated
Was this helpful?
At a high level, a Fabricate Account has the following structure:
The Free and Plus plans only allow one user per account.
A Fabricate account contains at least one user.
Enterprise accounts can have multiple users, and can use single sign-on (SSO) to manage user access. A user is assigned an account role, which determines the actions the user can perform in the account.
Accounts can optionally create account groups. A group is a collection of users. Accounts who use SSO can also optionally synchronize their SSO groups with their Fabricate account groups.
To use the Fabricate API, an account must have at least one Fabricate API key.
Accounts can have available domains to use for database workflows, SSO, and to write to Amazon S3.
Accounts can have available CA certificates to use to verify authentication to server connections.
The Free and Plus plans only allow one workspace per account.
Each Fabricate account contains at least one workspace. Enterprise accounts can have multiple workspaces. For example, each workspace might represent a different team.
When you create your Fabricate account, Fabricate automatically creates a workspace with your name. If you don't create other workspaces, then all of your databases are in that workspace.
Each workspace contains one or more projects.
You use projects to group your local databases and database connections.
Within a project, the Data Agent chat, workflows, plans, and mock API span the entire project, and can apply to any or all of the project databases.
For example, you can use a database connection to guide the structure of another database, or copy data between databases.
Local databases generate data within Fabricate. You can then export the data to other systems or use it to generate unstructured files.
Enterprise users can also create database connections, which are direct connections to external databases. You can then generate data directly to that database.
A workspace can be assigned a set of account groups, account users and API keys.
Each group, user, and API key is assigned a workspace role that controls their access to workspace functions.
Within a workspace, you can configure secrets to use to connect to account domains.
You can also configure custom skills for the Data Agent to use when it performs specific tasks.
Last updated
Was this helpful?
Was this helpful?