For the complete documentation index, see llms.txt. This page is also available as Markdown.

Create an application user

Create a non-personal application identity in DataOS.

Why use an application user?

When an action in DataOS runs under a personal user's identity, its access is tied to that person. If they leave the organization or change roles, anything running as them loses access.

An application user is a non-personal identity that you can provision with any role or permission: a role in a Tenant, access to Compute, Depots, Secrets, or any other use-case. You define what it can do based on what it is meant to represent, not who it is. Once set up, any person who needs to act under that identity simply gets runAsUser granted against this application user. They do not need individual access to each resource the application user holds.

This keeps access stable regardless of team changes, and avoids repeated per-person provisioning every time someone new needs to perform the same actions.

Before you start

Only an Operator can create users in DataOS, including application users.

Make sure you have:

  • DataOS CLI installed: follow the CLI setup guide if you have not done this yet.

  • CLI initialized and logged in: run dataos-ctl init and authenticate against your DataOS Instance. If you are unsure whether you are logged in, run dataos-ctl user get and confirm your own user appears.

  • Operator role: your account must have the Operator role assigned.

How to create an application user?

1

Create application user

Run the following command in the DataOS CLI:

dataos-ctl user create -n 'Data Product Developer' -t application -u dpdeveloper -e dpdeveloper@tmdc.io
INFO[0000] 🤠 user create...
INFO[0006] 🤠 user create...complete

          NAME          │     ID      │    TYPE     │        EMAIL        │         TAGS
────────────────────────┼─────────────┼─────────────┼─────────────────────┼──────────────────────
 Data Product Developer │ dpdeveloper │ application │ dpdeveloper@tmdc.io │ users:id:dpdeveloper
2

Verify user

Run this command:

dataos-ctl user get -i dpdeveloper
INFO[0000] 😃 user get...
INFO[0001] 😃 user get...complete

          NAME          │     ID      │    TYPE     │        EMAIL        │         TAGS
────────────────────────┼─────────────┼─────────────┼─────────────────────┼──────────────────────
 Data Product Developer │ dpdeveloper │ application │ dpdeveloper@tmdc.io │ users:id:dpdeveloper

The application user now exists in Bifrost under the Users tab filtered by type application.

Bifrost Users tab filtered by application type, showing Data Product Developer
Application users in Bifrost

At this point the user has no permissions beyond its own identity tag.

Tags tab showing only the users:id:dpdeveloper tag
Initial state: only the identity tag is present

The application user starts with minimal permissions. See Grant permissions to set up what the user can do and who can act under its identity.

Last updated

Was this helpful?