Changelog
What changed and what it means. Nothing here is a plan; it is all shipped.
Access for a period, taken back on time
- A reviewer chooses how long access lasts when they approve, or the agent's configuration decides. When the period ends the membership is removed in Microsoft 365 or Google Workspace and the person is told.
- Taking access away now reaches your directory as well as our policy store. Before this, a revocation removed only our own record.
- A page and an export list who currently holds what and when each piece ends. A reviewer can take access back early from the same page.
- Jira and Confluence can be read through a connector we run, with your own API token against your own site. Each tool is approved before an agent may call it.
- What an agent with no tool list may reach is now each organization's own setting. Organizations created from today start closed.
- The budget check no longer slows down as the month goes on.
Setup you can finish on your own
- Create your organization, choose what people can request, and set who approves, all from the product.
- The setup checklist now reflects what is actually done rather than what it remembered, and a step you skip stays skipped.
- Requests, approvals and the timeline behind them work end to end.
- Approved requests are written into your Microsoft 365 or Google Workspace group. Reviewers are emailed when something needs them, and requesters when it is decided.
One product, many companies
- Every row now belongs to an organization and the database enforces the boundary, so one customer's data is invisible to another by construction rather than by a query somebody remembered to write.
- Sign in with Microsoft or Google, or bring your own identity provider.
- Each organization runs against its own spend cap.