Need help with a step? Contact Iru Support.
How It Works
You select frameworks, refine controls and actions, attach evidence (manually or from Sources), and track readiness in framework and action views. Integrations can attach evidence automatically when they are connected and action descriptions name the system and evidence type clearly. As integrations and policy artifacts change, Adaptive Compliance can propose updates to control and action text. You review each recommendation and approve only the changes you want; audit periods and uploaded evidence are not changed by that workflow.Core Workflow: From Framework to Compliance
Framework Setup
Navigate to the Account Menu Button
In the sidebar, click the Account Menu Button (same flow as Recommended setup in Getting Started With Compliance).
Open Organization profile
Select Organization to open Organization profile. Iru may also prompt for this during framework setup.

Complete your company details
Fill in the fields that apply. For example: company logo, company name, business description, industry, business type, company size, company language, whether you have an IT department, and security team size. Keep this information current as your environment changes.
Add a framework and starting point
Click Add framework, choose a standard, then complete Select your [framework] starting point (generate, migrate, CSV, or manual). See Frameworks Management.

Control Management
Customize controls
Edit wording, add controls, or remove items so they match how your organization operates. When Sources or policy artifacts change later, check Home → Insights or Review Control Updates on a framework for Iru AI recommendations. See Adaptive Compliance.
Action Execution
Collect evidence
Upload artifacts or let connected Sources attach them when descriptions and permissions allow.
Evidence Management
Upload artifacts
Add files from Artifacts or from an action or control when the UI offers an upload.
Use sources
Connect Sources so integrations can attach artifacts when action text and permissions align.
Validate and link
Let validation run where the product supports it, then confirm artifacts sit on the right actions and controls.
Readiness Assessment
Integration Workflows
Automated Evidence Collection
Connect sources
Expand Compliance, select Sources, and turn on the toggle for each integration. See Sources Management for connector guides.

Write actionable descriptions
In each action, name the system and evidence type so connectors know what to fetch (see Actions Management).
Let sources sync
Sources refresh on a schedule; status and last sync appear on each source card. New, updated, or removed connections can prompt control update recommendations within about a day. See Adaptive Compliance.
Manual Evidence Upload
Choose files
Pick policies, exports, screenshots, or other files that satisfy the action or control.
Upload on Artifacts or the action
Add titles and descriptions when prompted, then upload (see Artifacts Management).
Collaboration Workflows
Team Coordination
Use comments and activity
Use comments for questions and the activity log to see what changed. For a tenant-wide view of compliance activity, see Unified Activity.
