diff --git a/_docs/administration/account-user-management/gitops-abac.md b/_docs/administration/account-user-management/gitops-abac.md index 98d7cc140..7fd83dfad 100644 --- a/_docs/administration/account-user-management/gitops-abac.md +++ b/_docs/administration/account-user-management/gitops-abac.md @@ -60,7 +60,7 @@ See the documentation for [codefresh_abac_rules](https://registry.terraform.io/p | Rule Element | Description | | -------------- | -------------- | |Teams | The team or teams to which to give access to the Application Entity. See [Adding users and teams]({{site.baseurl}}/docs/administration/account-user-management/add-users/).| -|Actions | The actions permitted for the application entity, and can be any or all of the following: {::nomarkdown} {:/} | +|Actions | The actions permitted for the application entity, and can be any or all of the following: {::nomarkdown} {:/} | |Attributes |Adding attributes, either individually or in combination, allow more fine-grained access control to enforce the _where_ policies for teams and actions.
Single attributes are useful to grant or deny access based on a specific property. For example, allow access to application entities on a cluster or within a namespace.
Combinations of attributes help enforce more complex access control. For example, require both a Runtime and a Label attribute to grant access to an application entity.
You can also add multiple instances of the same attribute with different values. For example, multiple Label attibutes with different values to sync application entities.{::nomarkdown} {:/} | diff --git a/_docs/deployments/gitops/applications-dashboard.md b/_docs/deployments/gitops/applications-dashboard.md index f958f50a7..d18a67ee7 100644 --- a/_docs/deployments/gitops/applications-dashboard.md +++ b/_docs/deployments/gitops/applications-dashboard.md @@ -510,6 +510,9 @@ Here's what you can see and do in the Summary tab: ### Logs for application resources In either Tree or List views, double-click an application resource to see its logs. Logs are available only for resource types such as pods. +>**NOTE**: +A disabled Logs tab indicates that you have not been assigned the permission to view logs for pod resource types. Contact your administrator for help. + {% include image.html lightbox="true" diff --git a/_docs/deployments/gitops/manage-application.md b/_docs/deployments/gitops/manage-application.md index 93cec4def..7da4d88ac 100644 --- a/_docs/deployments/gitops/manage-application.md +++ b/_docs/deployments/gitops/manage-application.md @@ -9,7 +9,7 @@ toc: true Application creation and deployment is one part of the continuous deployment/delivery process. An equally important part is optimizing deployed applications when needed. >**NOTE**: -The actions you can perform depend on the permissions assigned to you. +The actions you can perform depend on the [permissions]({{site.baseurl}}/docs/administration/account-user-management/gitops-abac/) assigned to you. * [Edit applications](#edit-application-definitions) @@ -27,8 +27,6 @@ The actions you can perform depend on the permissions assigned to you. * [Rollback applications](#rollback-gitops-applications) Rollback applications to previous deployment versions. -* [Rollback applications](#rollback-gitops-applications) - Rollback applications to previous deployment versions. * [Manage rollouts for deployments](#manage-rollouts-for-gitops-application-deployments) Control ongoing rollouts by resuming indefinitely paused steps, promoting rollouts, aborting, restarting and retrying rollouts.