What a service account is

A service account is an identity used by automations and integrations to reach Infinite Data without depending on a person.

When to use this

• Use it to understand when an automation needs an identity of its own.
• Use it before creating access for recurring processes.
• Use it in security reviews of integrations.

Before you start

• Identify the process that will use the account.
• Define an owner responsible for the account.
• List the data and actions genuinely needed.

Step by step

1. Assess whether the use is human or automated.
2. If automated, plan a service account with a clear owner.
3. Choose a name that indicates the purpose and the consuming system.
4. Attach the minimum roles and data rules.
5. Plan secret rotation and periodic review.

What happens next

• The account represents the automation in Infinite Data.
• The actions it takes are traceable in the audit trail.
• The account's owner has to keep its access and secret up to date.

Common errors

• Using a personal user account in an automation.
• Creating an account with no responsible owner.
• Granting broad access because the automation failed once.

Good practice

• A service account should have a single purpose and a clear name.
• Use least privilege and expiry where it makes sense.
• Revoke accounts that are not actively used.

Next steps

• When to use one
• Glossary