https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/installation/prerequisites/Recent content in Prerequisites onHugoenhttps://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/installation/prerequisites/accounts_and_permissions/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/installation/prerequisites/accounts_and_permissions/<p>Policy uses separate database logins, dependency users, and Kubernetes workload identities. These accounts serve different purposes and cannot replace one another. Protegrity Provisioned Cluster (PPC) administrators prepare dependency users before installation. Database operators prepare credentials for PostgreSQL inside the Policy stack.</p> <p>Use this reference with <a href="https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/installation/prerequisites/">installation preparation</a> and <a href="https://docs.protegrity.com/aiteam-edition/docs/gov_policy/policy/installation/">fresh installation</a>. Default Secret names below apply in the <code>pty-policy</code> release namespace. Use your configured names when the release overrides them.</p> <h2 id="database-accounts">Database Accounts</h2> <p>The chart defines default Secret names, but no default database usernames or passwords. Choose three distinct login names and independently managed passwords. The example usernames below are suggestions, not chart defaults. Each Secret contains <code>postgres_user</code> and <code>postgres_password</code>. The default database name is <code>policy</code>. Database provisioning also creates the fixed PostgreSQL <code>pmx_app</code> permission role and grants it to runtime. This <code>NOLOGIN</code> role is not a fourth login, platform user, or credential Secret.</p>