Add a mapping
Click Add mapping and fill in three fields.
The service user id is the one Guild recorded, so the reliable way to get it is to copy it from a security event in the audit log for a run that service started.
Mapping the same service user again on the same integration replaces the earlier mapping rather than adding a second one, and sets it back to Active if it was inactive.
The member has to be in the organization when you save. Guild refuses a mapping to someone who is not, rather than storing one that could never resolve.
Import mappings from a CSV
Click Import CSV to add many at once, either by choosing a file or pasting the rows. Each row is three columns — integration, service user id, Guild username or managed user handle — and a header row is optional.Review and retire mappings
The list shows one row per mapping:
Only Active mappings are used. Switch a mapping to Inactive to stop attributing that service user without losing the record of who they were, and switch it back to resume.
When a run is not attributed to a member
Guild falls back to the trigger’s creator when no active mapping matches the service user. A trigger created by an API key has no creator to fall back to, so the run is attributed to no member at all. A few events carry no person to attribute to and skip the creator fallback as well. A Slack message deletion is one: the event names no user, so a run it starts is attributed to the trigger rather than to anyone. A mapping also stops applying when the member leaves the organization. Guild re-checks their standing on every run and ignores the mapping if they no longer belong, so removing someone from the organization withdraws the attribution without anyone having to delete the row.Related pages
- Event triggers for the webhook-started runs that mappings attribute
- Service credentials for how the attributed member’s credentials are chosen
- Manage organizations for adding and removing organization members
- Slack and GitHub for connecting the services whose user ids you map