-
Notifications
You must be signed in to change notification settings - Fork 386
Michelle user access tokens update #913
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Added line about Org API Tokens being deprecated
|
The documentation is not available anymore as the PR was closed or merged. |
jeffboudier
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
mishig25
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm! Thanks a lot for providing the screenshots in dark and light modes
Co-authored-by: Mishig <dmishig@gmail.com>
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. |
Hi @mishig25 ! Could let me know if you think the screenshot updates are okay (since the official deprecation of Organization API tokens?) I've added the images to https://huggingface.co/datasets/huggingface/documentation-images/discussions/156.
Credit to @jeffboudier for the line: "If your user is member of an organization with read/write/admin role, then your User Access Tokens will be able to read/write the resources according to the token permission (read/write) and organization membership (read/write/admin)"
cc @jeffboudier @SBrandeis for viz since this doc update was reported by user via email