Repository navigation
feat(settings): add Resource Governance and group the Settings page - #3847
Merged
Merged
Conversation
Add an admin Resource Governance page at settings/resources. It lists every project and engine of the type chosen (insights included), sorted by display name, beside the one open, with tabs for Access (Bulk Access Management), Effective Permissions, Requests, Visibility, Audit Trail, SMSS, and Usage Limits for models. Access changes are applied or discarded before opening another resource. Rows can be checked and deleted together. The page opens on the first type, and its list stays in view while the page scrolls. Remove the App, Agent, & Skill, Database, Function, Guardrail, Model, Storage and Vector settings pages, their admin Bulk Access Management and Effective Permissions pages, and the detail headers and engine info the settings layout kept for them. Apps and engines are managed from their catalog pages. Group the Settings page tiles under Your Account, Resources & Access, Monitoring and Platform, add the Resource Governance icon, and give settings pages space at the bottom. Minor Changes: - move the General Platform Limit to a Usage Limits tab on Configuration - rename Apps to Projects in Member Settings, covering every project type - link team resources to their pages, with Copy ID - replace the tag field's browser suggestion list with a styled one
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add an admin Resource Governance page at settings/resources. It lists every project and engine of the type chosen (insights included), sorted by display name, beside the one open, with tabs for Access (Bulk Access Management), Effective Permissions, Requests, Visibility, Audit Trail, SMSS, and Usage Limits for models. Access changes are applied or discarded before opening another resource. Rows can be checked and deleted together. The page opens on the first type, and its list stays in view while the page scrolls.
Remove the App, Agent, & Skill, Database, Function, Guardrail, Model, Storage and Vector settings pages, their admin Bulk Access Management and Effective Permissions pages, and the detail headers and engine info the settings layout kept for them. Apps and engines are managed from their catalog pages.
Group the Settings page tiles under Your Account, Resources & Access, Monitoring and Platform, add the Resource Governance icon, and give settings pages space at the bottom.
Minor Changes: