Source
Governance, credentials & audit trail — found from sitemap — Appian
Checked for Appian on 13 Oct 2026
- Page
- https://docs.appian.com/suite/help/26.9/rbac.html
- Checked
- 13 Oct 2026, 16:56 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:9d67b3a23dd6dff78c0f0167770dc4f397078d40c436fa2479a4abd310a7eef1
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Rbac kubernetes configuration Report an error
“This page describes how to configure both the Appian operator Helm chart and Appian custom resources to customize Kubernetes RBAC to account for a variety of use cases. It is aimed at self-managed customers running Appian on Kubernetes.”
-
Rbac cluster wide access restriction Report an error
“When cluster-wide access is undesirable, you can restrict the operator's controllers to the appian-operator namespace only.”
-
Rbac multi namespace installation Report an error
“If you want to create Appian custom resources in other namespaces, you can also install the operator's controllers in each of those namespaces.”
-
Rbac aggregated cluster roles Report an error
“By default, the Appian operator Helm chart deploys ClusterRoles that aggregate to the built-in view, edit, and admin ClusterRoles.”
-
Rbac custom role binding Report an error
“Both the Appian operator Helm chart and Appian CRD support binding the operator and Appian, respectively, to arbitrary roles and cluster roles.”
-
Rbac pod security policy binding Report an error
“This is particularly useful when you need to make either the Appian operator or Appian use a specific pod security policy (PSP).”
-
Rbac appian cr spec fields Report an error
“The Appian operator and Appian CRD support binding Appian to existing ClusterRoles and Roles via the .spec.rbac.clusterRoles and .spec.rbac.roles fields, respectively, on Appian custom resources.”
-
Rbac rolebinding creation by operator Report an error
“When specified, the fields instruct the operator to create one or more RoleBinding resources that bind the provided ClusterRole(s) and/or Role(s) to the service account associated with the custom resource.”
-
Rbac operator default namespace install Report an error
“By default, the Appian operator should be installed once per cluster into the appian-operator namespace.”
-
Rbac rolebinding permission not granted by default Report an error
“The operator lacks access to do so by default.”
-
Copyright holder Report an error
“© 2026 Appian Corporation”
Scores citing this record
- The Data Protection Officer Governance, credentials & audit trail
- The Head of IT Governance, credentials & audit trail
- The Integration Engineer Governance, credentials & audit trail
- The Integration Engineer Governance, credentials & audit trail
- The Operations Analyst Governance, credentials & audit trail
- The Process Owner Governance, credentials & audit trail