19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
announcements
dagster-airbyte
dagster-airflow
dagster-bigquery
dagster-cloud
dagster-cube
dagster-dask
dagster-dbt
dagster-de
dagster-ecs
dagster-feedback
dagster-kubernetes
dagster-machine-learning
dagster-noteable
dagster-releases
dagster-serverless
dagster-showcase
dagster-snowflake
dagster-spatial
dagster-support
dagster-wandb
dagstereo
data-platform-design
events
faq-read-me-before-posting
gigs-freelance
github-discussions
introductions
jobs
random
tools
豆瓣酱帮
Title
z
Zach
09/12/2022, 9:05 PMone question and a small issue:
1. are user tokens scoped to a particular deployment? it's a bit confusing because users are added per-deployment, but if I create a user token in one deployment it shows up in the "Configure tokens" tab in the other deployment
2. when I try to create a token for another user the token doesn't appear in their list of tokens. when I refresh the page though the new token appears in my own list of tokens, instead of the target user's token list
I'm also the org admin in case that makes a different for managing other users' tokens
b
ben
09/12/2022, 9:13 PMUser tokens are deployment-scoped, yes.
Even as an admin, you are unable to create user tokens for other users - the UI is probably a bit misleading here since the dialog is always set up to create a token for yourself. We should hide that button in the case that you’re viewing another user.
z
Zach
09/12/2022, 9:15 PMokay, that clarifies things. thanks!
it also seems like the UI shows all tokens across all deployments, which is a bit confusing - it'd be nice if it only showed the tokens that are scoped to the deployment that's selected
b
ben
09/12/2022, 9:29 PMAhh I misspoke - they are not deployment-scoped! Sorry for the confusion
they’re equally permissioned to the user on each deployment, e.g. if I create a token for my user, who is a viewer on deployment A and admin on deployment B, the token will be usable on both & will have viewer perms on A and admin on B
z
Zach
09/12/2022, 9:30 PMah okay, got it. thanks!