Skip to content
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

docs: add runner role to rbac docs #46916

Merged
merged 2 commits into from
Oct 15, 2024
Merged

docs: add runner role to rbac docs #46916

merged 2 commits into from
Oct 15, 2024

Conversation

teallarson
Copy link
Contributor

What

We are adding a new role of Runner to both the Organization and Workspace level (Internal Platform PR). This PR updates the documentation to reflect those changes.

Copy link

vercel bot commented Oct 15, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
airbyte-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 15, 2024 4:36pm

@octavia-squidington-iii octavia-squidington-iii added the area/documentation Improvements or additions to documentation label Oct 15, 2024
@teallarson teallarson marked this pull request as ready for review October 15, 2024 14:21
@@ -7,28 +7,29 @@ products: oss-enterprise, cloud-teams
Role Based Access Control allows a user with Administrative access to apply roles to users, granting different levels of permission within an Organization or Workspace.

:::info
**Self-Managed Enterprise** instances have an `Instance Admin` role in addition to the other roles outlined in this document. The first user who logs on to Airbyte in a Self-Managed Enterprise instance will be assigned this role. This user will have all permissions listed below for all workspaces and all organizations associated with their Enterptise account. To update this assigment, enterprise customers should contact [Airbyte support](https://support.airbyte.com/hc/en-us).
**Self-Managed Enterprise** instances have an `Instance Admin` role in addition to the other roles outlined in this document. The first user who logs on to Airbyte in a Self-Managed Enterprise instance will be assigned this role. This user will have all permissions listed below for all workspaces and all organizations associated with their Enterprise account. To update this assignment, enterprise customers should contact [Airbyte support](https://support.airbyte.com/hc/en-us).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice

| ---------------------- | :--------: | :--------:| :--------:| :--------: |
| **Read Workspace**<br /><ul><li>List the connections in a workspace</li><li>Read individual connections</li><li>Read workspace settings (data residency, users, connector versions, notification settings) </li></ul> | X | X | X | X |
| **Modify Connector Settings**<br /><ul><li>Create, modify, delete sources and destinations in a workspace</li></ul> | | | X | X |
| **Sync Connection**<br /><ul><li>Start/cancel syncs and refreshes</li></ul> | | | X | X |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image should include runner here i think

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Totally. Fixed in 089ba77 and re-ordered the rows so we have a cleaner shape.

@teallarson teallarson merged commit de6eeaa into master Oct 15, 2024
31 checks passed
@teallarson teallarson deleted the teal/add-runner-to-docs branch October 15, 2024 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants