You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the time I created this issue, the Resource Requests guide is 668 lines long, and over half of these are in the "Next Steps" section. We should move this content out of the Resource Requests how-to guide to make it easier for users to discover this content—and for us to expand this content as we develop Teleport's Access Request capabilities.
How will we know this is resolved?
The information in the "Next Steps" section of the Resource Requests guide (as of the time this issue was created) is in a more appropriate place.
Related Issues
#33414 adds an Access Request configuration guide. We can find a way to work this information into that guide.
The text was updated successfully, but these errors were encountered:
Closes#33417
Focus the guide more on its stated topic by moving tangentially related
reference information at the end of the guide to more appropriate pages.
- Replace the `search_as_roles` section with a link. Much of the "Next
steps" section is a long list of examples of Teleport roles that an
admin could assign to `search_as_roles`. This is unnecessary, since a
user familiar with a Teleport role won't need this information to
understand `search_as_roles`. It is not the job of the Resource Requests
guide to teach users about Teleport roles.
- Condense the "Next steps" guidance. There are "Next steps" sections.
Make them one. Also turn the section re: Access Request plugins into a
bullet.
- Move instructions for searching for and requesting Kubernetes
resources into the tsh guide. These instructions are end users, so
move them to the appropriate guide to make them more discoverable.
Closes#33417
Focus the guide more on its stated topic by moving tangentially related
reference information at the end of the guide to more appropriate pages.
- Replace the `search_as_roles` section with a link. Much of the "Next
steps" section is a long list of examples of Teleport roles that an
admin could assign to `search_as_roles`. This is unnecessary, since a
user familiar with a Teleport role won't need this information to
understand `search_as_roles`. It is not the job of the Resource Requests
guide to teach users about Teleport roles.
- Condense the "Next steps" guidance. There are "Next steps" sections.
Make them one. Also turn the section re: Access Request plugins into a
bullet.
- Move instructions for searching for and requesting Kubernetes
resources into the tsh guide. These instructions are end users, so
move them to the appropriate guide to make them more discoverable.
Applies To
docs/pages/access_controls/access-requests/resource-requests.mdx
Details
At the time I created this issue, the Resource Requests guide is 668 lines long, and over half of these are in the "Next Steps" section. We should move this content out of the Resource Requests how-to guide to make it easier for users to discover this content—and for us to expand this content as we develop Teleport's Access Request capabilities.
How will we know this is resolved?
The information in the "Next Steps" section of the Resource Requests guide (as of the time this issue was created) is in a more appropriate place.
Related Issues
#33414 adds an Access Request configuration guide. We can find a way to work this information into that guide.
The text was updated successfully, but these errors were encountered: