Skip to main content
See what is happening

Apps and automations

Some AI use is not a person. An internal tool that calls an AI vendor with API keys, or a scheduled job, sends its activity with no person to blame, so every record shows "Not attributed". Create an…

Written By Christopher Scaminaci

Last updated 4 days ago

Some AI use is not a person. An internal tool that calls an AI vendor with API keys, or a scheduled job, sends its activity with no person to blame, so every record shows "Not attributed". Create an application or an automation for it and tell StackJack which activity is its. From then on that activity shows under its name in the Activity explorer, on Findings and on Alerts.

At a glance

  • What it does: attributes machine use to a named application or automation.
  • Plan: every plan. Free includes 2, Pro 5 and Business 15. Enterprise, the plan StackJack assigns, has no limit.
  • Who: an Administrator creates and changes them. Reviewers and Reveal approvers see the list.
  • Where: AI Governance → People → Apps and automations.
  • Needs: a source that sends the activity.

What it costs

Apps and automations are free up to the number your plan includes. Each one past that counts as one staff seat, and is charged the way a staff member above your plan is charged. Billing shows how many you use. An application counts in a billing period when it had activity in it. See AI Governance billing.

Create one

  1. Open People → Apps and automations.
  2. Under Add an application or automation, enter a name, choose Application or Automation, and add what it is for if you like.
  3. Select Add it.

Names are unique among your applications and automations, without regard to case.

Tell StackJack which activity is its

Open the application and add a match. A match says which activity belongs to it. Activity that names a person always stays with that person.

Match byWhat it matches
Service nameRecords from one source that carry a service name, for example the service.name an OpenTelemetry sender reports.
Everything from one sourceEverything that source sends that names no person.
Vendor API keyUsage the vendor reports for one API key (Anthropic or OpenAI). Enter the key's id from the vendor, never the key.
Sign-in idAn end-user id the application sends.
Email addressAn email address the application sends.

A service name is matched before a whole source, so one source can feed several applications. A match belongs to one application. If another application already has it, StackJack tells you which one and asks before it moves the match. A person's identity on your roster is never moved to an application.

Past activity

Adding a match changes what is recorded from now on. To attribute what was already recorded, select Apply to past activity next to the match. StackJack attributes the records that match and name no person, updates the usage totals for the hours and days they sit in, and tells you how many it changed. This can take a while. If it says there is more, run it again.

Past records carry a service name only from the day this feature started, so a service-name match covers earlier days only through a whole-source match. A sign-in or an email match does not find past records, because they were recorded under the person that sign-in became. Use Merge into for that.

Detected sign-ins

When a sender reports a user id that nobody on your roster owns, StackJack records it as a person. Detected sign-ins that may be applications lists those, by a generated label and with their recent activity. If one is really a bot or a service:

  • Turn into changes it into an application or an automation. Its history stays with it.
  • Merge into moves its sign-in to an application you already have and counts it as that application. Its past activity is not changed.

A person on your roster, or one that holds a directory sign-in, is never listed or changed.

Attribute from the Activity explorer

You can also start from a record. Open it and select Attribute to.... See The Activity explorer.

Archive one

Archiving stops an application collecting new activity and releases its matches, so another application can use them. Its past activity keeps its name.

What you will see

  • The application's name, followed by "(application)" or "(automation)", wherever a person's name would be.
  • Applications are not in the People list and are not counted as people using AI.
  • Every change is recorded in the audit trail with ids and counts, never a name.

Troubleshooting

What you seeWhat to check
Activity is still "Not attributed"Add a match, then select Apply to past activity for earlier days. A record that names a person is never moved.
"Another record already holds that match"Confirm the move, or remove the match from the other application first.
"You already have an application or automation with that name"Choose another name.
You cannot add anotherAn organization holds at most 200. Archive one you no longer use.

Next