Employees ask June directly.
Employees ask June for the software they need. June checks eligibility and follows the policy you’ve set for that access.
Your team asks June. Your policies decide who gets access, who approves it, and when it ends.
Access
Intelligence
Resources
Give people the tools they need, on your terms.
| Application | Policies | Approvals | Access length | |
|---|---|---|---|---|
| NotionKnowledge & collaboration | Workspace access | Automatic | Ongoing | |
| FigmaDesign | Design teamProject editor | By policy | By policy | |
| LinearProject management | Engineering access | Manager | Ongoing | |
| Adobe Creative CloudCreative tools | Design teamProject access | By policy | By policy | |
| AsanaWork management | Team memberProject guest | By policy | By policy | |
| 1PasswordSecurity | Employee vaults | Manager | Ongoing | |
| LoomVideo messaging | Creator access | Automatic | Ongoing | |
| ZoomMeetings | Meeting hostWebinar host | By policy | By policy |
Employees ask June for the software they need. June checks eligibility and follows the policy you’ve set for that access.
Route through one approver or several. Set reminders and escalation so a request doesn’t sit waiting for someone to chase it.
Give people access for the work at hand. June grants it when the policy is satisfied and removes it when the time is up.
From everyday apps to temporary project access, decide what should happen before a request arrives.
A design seat for the people helping bring a project to life.
Confirm the project need
Application owner · Design
Reminders and escalation start with each approval step.
Employees ask June in Slack. Your policy takes care of the approvals, the access, and when it ends.
Employees can send June a direct message in Slack. June matches the request to an application policy, collects any required context, and follows its approval and fulfillment steps.
Yes. An application can have multiple policies with different eligibility rules. Limit a policy by employee type or department, and choose the duration and justification each request needs.
Yes. For policies that don’t require approval, June can grant access automatically when the requester meets the eligibility rules. Other policies can require a manager, an application approver, or named employees.
Configure a nudge and an escalation route for each approval step. June follows those timings and routes the request to the next configured approver. An unanswered request isn’t treated as an approval.
Yes. Set a time limit and configure the corresponding revoke action. June grants access after the required approvals and removes it when the access period ends.
Each policy defines grant and revoke actions using your connected tools. The examples above add and remove employees from Okta groups. June notifies the requester when their access is ready.