Overview
This page explains the basic procedures for setting up a policy from creation to activation.
You can create a policy using a preset or create one from scratch. If you are setting up a policy for the first time, we recommend starting with a preset that matches your goal.
For an overview of the feature, see "What is Policy Feature?".
Prerequisites
Creating or editing policies requires Josys Super Admin permissions. Please check the following points before starting the setup.
| Check Item | Details |
|---|---|
| User Information | To trigger processes based on onboarding or offboarding, ensure that statuses, start dates, end dates, etc., are registered correctly. |
| App Integrations | To perform automated account operations, the integration with the target app must support those operations. |
| Notification Channel Integration | To send access confirmation notifications via Slack, complete the Slack integration in advance. |
| Target Scope | Determine in advance the users, apps, and actions to be processed. |
Available setting items and actions vary depending on the policy type and the target app. This page explains common basic operations.
1. Select Creation Method
Go to "Policies & Automation" > "Policies" from the left menu and start setting up using one of the following methods.
Set Up from a Preset
- Turn on "Show Standard Policies".
- Filter by category on the left, and open a preset that matches your goal.
- Click "Configure & Enable".
- Review the pre-filled settings, and configure the target apps, confirmation recipients, etc., to match your organization's operations.
Presets are not activated simply by opening them. Be sure to review and save the settings.
Create New
- Click "+ Policy" at the top right of the screen.
- Select a category that matches your goal on the "Select Policy Type" screen.
- Fill in each configuration item.
After completing the settings on each screen, click "Next" to proceed.
2. Set Up Triggers
A trigger is an event that initiates policy processing.
Depending on the selected category, set triggers such as onboarding/offboarding, account usage status, or permission changes. If input fields such as number of days or status appear, specify them according to your operations.
Even when using a preset, check whether the pre-filled trigger matches your goal.
3. Set Up User Conditions
Specify the scope of users covered by the policy.
| Selection | Details |
|---|---|
| All Users | Targets all users who meet the criteria, such as triggers. |
| Identity Groups | Specifies targets by including or excluding groups. |
| Custom Conditions | Specifies targets based on criteria such as Departments, domain, job title, Work Locations, or user category. |
In Identity Groups, users belonging to both included and excluded groups will be excluded from the target scope.
If you set multiple custom conditions, users who meet all conditions will be targeted. You can also specify multiple values for a single condition.
Example: Target users whose "Department is Sales" AND "Work Location is Tokyo".
4. Set Up App Conditions
Specify the apps covered by the policy.
Only apps that can provide the information required for policy evaluation can be selected. For example, apps that provide last login dates appear in Unused Account Management, while apps that provide permission info appear in Privileged Access Management.
If multiple instances of the same app are integrated, check the integration name before making a selection.
For policies targeting Discovered Apps, target scope may be specified by app attributes such as risk level or category.
5. Set Up Access Confirmations
Configure this setting if you want to confirm the necessity of access with users or reviewers before executing actions.
If you do not use access confirmations, proceed to the next step.
Select Respondents
Under "Review Type", select who should respond.
- The user themselves who uses the target app
- App reviewers/owners
When requesting app reviewers/owners, specify respondents for each target app.
Check Questions
The primary question and answer choices are pre-filled based on the category and trigger. Check if the content suits your operations.
You can also add questions using "Add Additional Question" to gather information needed for decision-making.
Only answers to the primary question are used for action branching. Answers to additional questions are not used for branching.
Set Up Notifications and Reminders
Set up the notification method, title, and body. Prior integration is required to send notifications via Slack.
Set up "Send Reminders" as needed. Reminders will be sent to respondents who have not yet answered.
6. Set Up Admin Consent
Select whether admin approval is required before executing actions.
| Option | Behavior |
|---|---|
| Admin consent not required | Proceeds to the action corresponding to the response without requiring admin approval. Example: Deleting an account responded to as "Not needed" in the access confirmation without additional approval. |
| Admin consent required | Proceeds to the configured action only after receiving admin approval following the access confirmation response. Example: Deleting an account responded to as "Not needed" after an admin approves it. |
If admin consent is required, set up approvers. You can assign different approvers for each app. If multiple approvers are configured, approval by any single approver allows the process to proceed.
7. Set Up Actions
Click "Add Action" to select the operations to execute.
In addition to account operations, you can set up email notifications, manual task creation, Service Requests creation, and more. Available actions depend on the policy type and target apps.
For details on each action, see: About Available Actions
Once an action is selected, configure the target, assignee, message body, etc., according to the displayed fields.
If automated account operations are not available, you can assign manual tasks or Service Requests to request action from an assignee.
Set Up Actions for Each Response
When using access confirmations, set up actions for each response to the primary question.
For example, for the question "Is this account still required for business operations?", you can configure different responses as follows:
| Response | Configuration Example |
|---|---|
| Yes | Do not set a deletion action to keep the account. |
| No | Delete the account. |
| Don't know | Create a manual task for an assignee to review. |
| No response | Configure the action to take if no response is received within the specified period. |
For "No response", specify the number of days to wait for a response. If no response is received within this period, the process moves to this branch.
Actions in each branch are also processed according to the configured admin consent and execution timing.
Set Up Execution Timing
For actions such as account deletion, you can select the following execution timing options:
| Option | Details |
|---|---|
| Execute Immediately | Executes immediately after required confirmations and approvals are completed. |
| Specify Execution Date | Executes after a specified number of days has passed since required confirmations and approvals were completed. |
The value entered in "Specify Execution Date" is the number of waiting days, not a calendar date. The waiting days are counted from the date of the access confirmation response or the admin approval date.
Use Variables in Messages
In message text for manual tasks, emails, and Service Requests, you can insert dynamic information such as user names and app names using variables.
Check available variables on the message input screen.
8. Review and Save Settings
Review the following details in "Policy Details":
- Policy Name
- Triggers and target users/apps
- Access confirmation respondents and questions
- Admin consent requirement and approvers
- Actions and execution timing for each branch
After reviewing, select Enabled or Disabled status and save. You can also save the configuration as disabled and enable it later.
When Targeting Existing Events
Settings configured to target existing events will also detect targets that met the criteria prior to policy creation.
For policies targeting Discovered Apps, existing events currently cannot be excluded. Enabling the policy will trigger existing targets immediately, so please confirm the target scope and actions to be executed beforehand.
For Discovered App policies that detect the use of unapproved apps, the policy runs only once for each combination of user and app. If the same user uses the same app again, the policy does not run a second time. Even if recent usage appears on the Discovered App details screen, the policy does not run if it has already run for that user and app.
Check Execution Status
You can check the execution status and history of processes based on saved and enabled policies from the "Automation" menu.
If admin consent is configured, manage approvals in "Action Centre". If actions to create Service Requests are configured, you can review created tickets on the "Service Requests" screen.
Edit, Disable, or Delete Policies
| Operation | Method |
|---|---|
| Edit | Change settings via "View" > "Manage Policy" in the policy list. |
| Enable / Disable | Toggle the switch in the policy list. |
| Delete | Select "Delete Policy" at the bottom of the details screen. |
After making changes, review and save the configuration.