Which items may use a credential

Updated Nov 17, 2026
DataMagik Automate

Limit a credential to the scripts and automations that need it, at the level they need.

Any item, or only listed items

On the credential's rules page, Items tab, under Which items can use it:

  • Any item in company (the default): every script and automation in the company can use it. This is how credentials have always worked.
  • Only the items listed below: anything else that asks for it is refused and logged. A credential limited to listed items cannot be the company's default credential: make another credential the default first.

Who can do this: the credential's stewards.

Add an item and choose what it can do

  1. Under Allowed items, pick the item in Add item.
  2. Choose what it Can do.
  3. Press Add.

List the items first, then switch to Only the items listed below, so nothing that needs the credential is left out.

LevelWhat the item may do
Read from PlexThe platform signs the item's Plex calls that read. The item never sees the password.
Read and writeThe platform signs the item's Plex calls, including ones that change data. The item never sees the password.
Read the passwordThe script itself gets the value. Each new version of its code waits for a steward's approval before it is published; the approved version keeps running meanwhile.

The Allowed items table also shows the Approved version, Uses, 30 days (and how many uses the rules would refuse) and Last used for each item.

Prefer a level that never reveals the password. For an API key, give it allowed hosts and send it with fetch(url, {credential: "NAME"}). The item then needs no Read the password at all.

Read the password: approval is tied to the code

An item with Read the password is approved for its code exactly as a steward reviewed it.

  1. A builder saves a new version of the script. It is saved but not published: Saved as version N, but not published: this script reads a credential's password, so a steward must approve this version first. The current version keeps running until then.
  2. The stewards are notified. The version and its code fingerprint show on the credential's Items tab.
  3. A steward approves it, and the version is published. If the script reads several credentials' passwords, each credential's steward approves for that credential, and the version is published when none is waiting.
  • While a version waits, its code cannot be changed.
  • If the code changed after the request, the approval is refused: The code changed since this request, so it was not approved. A new request is needed for the code as it is now.
  • Code that runs without an approved fingerprint, for example code edited in place, gets no password. The item row then says the version runs and nobody has approved it.
  • Test runs get the password only when the person testing is a steward.

In Sites, the parent company can forbid Read the password altogether with Never allow "Read the password" in Sites.

Requests

Items ask to use a credential in two ways:

  • From the script editor: a builder presses Request access. The script must be saved first.
  • From a copy sent to a Site: when a copied item needs a Site credential that is limited to listed items. The item arrives switched off and the request shows on the Site's setup checklist.

Requests show on the Items tab marked Asks to use it, with who asked and when. A steward presses Approve or Decline. All stewards (or, with none named, the company's admins) get an in-app notification, An item asks to use a credential, and an email.

Troubleshooting

"… can only be used by the items listed on it, and this item is not one of them"

The credential is limited to listed items. Ask a steward to add the item, or press Request access in the editor.

"… and its grant for this item only reads"

The item is listed with Read from Plex but tried to change data. Ask a steward to change its level to Read and write if that is intended.

"… this version of the item's code has not been approved by a steward to read it"

The script reads the password and its current code is not approved. Ask a steward to approve the waiting version on the Items tab.

Was this page helpful?