About Attio
Iru reads workspace, object, record, and membership data from Attio’s REST API using a Bearer token created under Workspace Settings → Developers. Tokens are scope-bound at creation - grant read paths your controls require and avoid unnecessary write scopes.How It Works
Official references: REST overview, Authentication, Generating an API key.
Prerequisites
- Workspace admin: only admins create tokens.
Connect Attio to Iru
- Attio
- Iru Compliance
Complete this tab before you connect the source in Compliance.
1
Open Workspace Settings
In Attio, open the Workspace menu (workspace name or icon), then choose Workspace Settings.
2
Open Developers
Select Developers (or Developer settings) for the workspace you want Iru to read.
3
Create a new access token
Select New access token (or Create token). When prompted, enter a name such as Iru Compliance so you can audit the integration later.
4
Choose read scopes
Enable read scopes that cover the objects your compliance program needs (for example records, lists, or notes; match your Attio plan and internal policy). Avoid write scopes unless your security team explicitly requires them.
5
Create and copy the token
Create the token and copy the value once when Attio displays it. Store it securely; you will paste it into Iru as the Bearer token.
Continue on the Iru Compliance tab.
Troubleshooting
Nothing opens when you turn the source on
Nothing opens when you turn the source on
Check pop-up blocker settings for the Iru site and try again.
Missing objects
Missing objects
Create a token with broader read scopes for those objects.
Related Articles
Sources Management
Browse and manage every Compliance source.
Getting Started With Compliance
Frameworks, actions, and Artifacts.
Iru Overview
How Endpoint, Compliance, and Identity fit together.
Artifacts Management
Upload, review, and organize evidence from sources and actions.