Skip to main content
A service account is a non-human identity for an AI agent, script, or automation that connects to Layers. It has its own client ID and secret and its own role on each store you add it to. Use one when an automation should keep working regardless of who set it up, or when you want its access to be separate from any teammate’s. Service accounts connect to the Layers MCP server. They can’t sign in to the Layers dashboard.

Prerequisites

  • You need the Invite members, assign roles, manage custom roles permission on the store. The Owner and Admin roles include it.
  • You can only give a service account permissions you hold yourself.

Create a service account

  1. Go to Settings > Service accounts, under Access & Security.
  2. Click New service account.
  3. Enter a Name that describes what the account is for, such as “Catalog sync agent”.
  4. Select one or more roles, and optionally add extra permissions, including resource-scoped permissions.
  5. Click Create.
  6. Copy the Client ID, Client secret, Token URL, and MCP URL from the dialog and store the secret somewhere safe.
The client secret is shown only once. If you lose it, rotate the secret to get a new one.
The account keeps the permissions you granted even if your own access changes later.

Review service accounts

The Service accounts page lists each account with its client ID, its roles on this store, and when and by whom it was created. Accounts that can publish changes without review show a Publishes without review badge. An account that belongs to your store but has no role on it shows Not on this store. Service accounts also appear in their own section on Settings > Users & Invites, marked with a bot badge. They don’t count as team members and don’t receive invites or notifications. Select Manage there to open the Service accounts page.

Change what a service account can do

Open the account’s actions menu and select Change access to update its roles and extra permissions on this store.

Publishing without review

By default, changes a service account makes through the shared editor go to a person for review, just like changes from an AI assistant connection. To let an account publish its changes straight to your live store, give it the Publish without review permission in the Access group, along with the edit permission for each resource it changes. This permission only affects service accounts.

Use a service account on more than one store

If your store belongs to an organization, a service account created on it belongs to the organization and can be added to the organization’s other stores. Open the account’s actions menu on another store’s Service accounts page and select Add to this store, then choose its role there. Each store has its own role for the account. To take an account off one store, select Remove from this store. It loses its role on that store, but its secret keeps working on its other stores. Detaching a store from the organization also removes the organization’s service accounts from that store. Organization owners and admins can see every service account in the organization. To manage an account that is on several stores, you need access management permission on each of them.

Rotate a secret

Rotate a secret when it may have been exposed, or as part of a routine security review.
  1. Open the account’s actions menu and select Rotate secret.
  2. Confirm. A new secret is shown once; copy it.
  3. Update the automation with the new secret.
Rotation takes effect immediately. The old secret and every token created with it stop working right away, with no grace period.

Revoke a service account

Revoke an account when the automation it belongs to is retired. Open the account’s actions menu, select Revoke, and confirm. Its tokens stop working on every store and no new tokens can be issued. Revoking can’t be undone. The account stays in the list with a Revoked badge so its history remains visible.

Rename a service account

Open the account’s actions menu and select Rename. Renaming doesn’t change its credentials or access.

Troubleshooting

The automation gets a permission error. The account’s role on that store doesn’t include the permission the action needs, or the account hasn’t been added to that store. Select Change access or Add to this store to fix it. The automation stopped connecting after a rotation. Update it with the new secret. Secrets from before the rotation no longer work. You can’t grant a role or rotate a secret. You can only grant, and rotate secrets for, permissions you hold yourself on every store the account belongs to. Ask an Owner or Admin to make the change.

Next steps