**Non-blocking — follow-up needed for consistency**

After #5282 I think there are a few pages that might also need updating

Non-blocking — follow-up needed for consistency

This PR documents that Global Admin can never assign Finance Admin, but several other pages still describe Global Admin's role-assignment ability without that carve-out. Filing as non-blocking; we'll ship this PR and address these in a follow-up:

• docs/cloud/manage-access/users.mdx:103-104 — "With Global Admin or Account Owner privileges, you can update any user's account-level role..." doesn't mention the Finance Admin exception.
• docs/cloud/manage-access/user-groups.mdx:44 and :91-92 — group role administration is described as available to Global Admin without exception.
• docs/cloud/manage-access/service-accounts.mdx:37, :68 (Create a Service Account), and :194-213 (Update a Service Account) — these flows and CLI examples let a Global Admin pick any Account Level Role, including Finance Admin.
• docs/cloud/manage-access/permissions-reference.mdx:373 — "Manage unscoped (account-level) service accounts" doesn't carve out the Finance Admin restriction for Global Admin.

Originally posted by @Duncanma in https://github.com/temporalio/documentation/issues/5282#issuecomment-5733349516

Start with the cited passages in docs/cloud/manage-access/users.mdx, user-groups.mdx, service-accounts.mdx, and permissions-reference.mdx, then compare their role-assignment wording with the restriction documented in #5282. Update the affected descriptions and CLI examples so Global Admin's inability to assign Finance Admin is represented consistently. Done means all listed pages reflect the same exception.