Company-domain sign-in
Google sign-in can be restricted to the configured company domain. User deactivation prevents future access, while historical records remain available.
Security & privacy
Clear controls. Visible responsibility.
Understand who can access the work, what information is collected, and how operational evidence is recorded. Trust starts with specifics.
Designed into the workflow
The right context. The right access.
IssueLane connects sensitive operational information with the people responsible for it. These controls are implemented in the product; deployment configuration, hosting, and integration choices determine how they operate for your organization.
Access by responsibility
Employee, department, and administrator permissions control access to requests and operational records. Server-side checks enforce permissions on protected actions.
Controlled file access
Attachment downloads require authorization. Supported uploads are validated, and S3-backed downloads can use time-limited signed URLs.
Collection you can explain
The device privacy page describes collected information from the served query pack. Supported usage collection can be disabled through device settings.
Scoped connections
AWS and GitHub integrations use read-only external access. Device agents use per-device credentials with rotation. API keys support controlled custom connections.
A record of the work
Ticket histories and audit records capture actions and decisions. Access reviews, offboarding records, and reports contribute to evidence gathering.
Evidence, close to the work
Prepare with the records you already maintain.
Export evidence for 13 selected controls mapped in the product to SOC 2 and ISO 27001 references. Bring device checks, access reviews, offboarding, and security findings into a printable report and CSV exports.
These mappings support audit preparation. They do not establish certification or complete coverage of either framework.
Asset inventoryEvidence source
Device encryption & firewallEvidence source
Vulnerability managementEvidence source
Periodic access reviewsEvidence source
Offboarding follow-upEvidence source
Cloud, code & AI tool findingsEvidence source
Before you roll out
Make the details part of the conversation.
Discuss your hosting requirements, data handling, access model, and integration scope during the demo. Confirm support, retention, and deployment commitments for your organization before rollout.
AI and device visibility
AI-assisted triage and invoice extraction include review steps. When enabled, the relevant input is processed by the configured AI provider.
Device findings support monitoring and tracked follow-up. They do not imply remote wipe, automatic patching, or inspection of every AI connection.
See how your team’s work connects
Keep work
moving.
Bring employee support, assets, and operational follow-up into one workspace—with a clear owner for every next step.