Get Started with Identity Flows

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Idira Success Blogs
4 min read
L4 Transporter
GET STARTED WITH IDENTITY FLOWS

Automate identity management workflows with Identity Flows, a no-code visual editor to orchestrate identity events, build workflows, and synchronize identity data.

Flows Pre-Implementation Checklist:
Flows Rollout Plan:
  • Implementation: Start by identifying two items in your company: which process is the most painful in your organization and which would be the simplest to solve. Implement a simple Flow for a quick win to get accustomed to how Flows work. This might look like setting up a Slack notification after an event in Salesforce or emailing HR when a user completes a task.
  • Step 1: Build the Plan: Start by deciding the desired outcome. Identify the triggers needed for each step, including the necessary software, action, or event. Sometimes, a step might be an if/then statement, causing your diagram to fork. Identity Flows can easily accommodate this situation, too. Note the variables in your plan.
  • Step 2: Identify the Stakeholders and Admins: To complete the authentication process for each connector in Flows, you'll have specific access to that piece of software. In most cases, Flows will need permission to access the API of each application included in your automation. What operations can be executed in the third-party apps are defined by connectors. You'll need to identify who in your organization will have access to the necessary permission level to integrate each application into Flows. For example, HR applications often have a process for accessing their APIs, so getting started early will save time later.
  • Step 3: Build your Draft Flow: You're finally ready to create a Flow. Consider starting with a Flows template. Templates are a terrific way to save time with automations that are the same or like the ones in your plan. With a few clicks, you can use the import feature to bring the json template straight into Identity Flows. Whether you start with a template or drag an endpoint into the Flow, Flows will read the connector for desired authentication types. You must authenticate through an Authorization before running or testing the Flow. An Authorization is usually already configured; you will need to name it and insert your credentials. It is common for a step in your automation to use information retrieved in an earlier step. Using the fields under the Map column will allow this.
  • Step 4: Test your Flow: If possible, test using nonproduction data or make changes that do not re-enter production. You may have done this in your previous step by creating an Authorization with UAT credentials. You may be able to do this by inputting production data but applying the transformations or outputs to a sandbox. How you test will depend on your Flow and your apps, but planning accordingly and running iterations outside your production environment is essential. Flows easily allow tweaks and changes in the GUI for quick updates. After any changes or updates, you can run the Flow using the Play button and check for failure or success in the notification dropdown. You can open each dropdown and drill in for more information during your test.
  • Step 5: Roll out: Now that your automation is tested and ready for production, it's time to communicate the rollout with your end users. But what do they need to know? It's best practice to communicate these changes before they go live, providing users ample time to become accustomed to the process and ask questions.

Flows Resources:
  • 2604 Views
  • 0 comments
  • 0 Likes
Top Liked Authors