In this blog post, you will know how to update Organizational Units (OU) based on departments using the powerful capabilities of the Foresight Automation tool. In today's fast-paced business landscape, maintaining an efficient organizational structure is crucial for success. As departments evolve and grow, it becomes necessary to update and align organizational units accordingly. With the advent of advanced automation tools like xFanatical Foresight automation tool, this process can be streamlined and made significantly more efficient.
Understanding the Relationship Between Organizational Units and Departments
Organizational Units (OU) represent different divisions, teams, or functional areas within a company. On the other hand, departments are responsible for specific functions or areas of expertise. These two elements are interconnected, as organizational units are often aligned with departments to ensure clear reporting lines, effective communication, and streamlined decision-making.
Update Organizational Units Based on Departments with Foresight
xFanatical Foresight automation helps you to automate and streamline your regular business workflows and Google Workspace workflows systematically. As a Google Cloud partner, it also provides automated solutions for Google Workspace operations. Its cost-effective, time-saving, and productive functionalities empower the Good Admin and users to perform their tasks effortlessly.
Admin can update OU based upon the organizational unit through the Google Admin console by creating users’ CSV files. However, there is no specific feature in the Admin Console regarding this. So, Foresight has created this feature for the Admin and automates this process to save more time and manage administrative policies efficiently for the Admin.
Video Demo
Instruction
Rule 1: Bulk update users’ OU based on their department information. This rule exports users with a CSV file having two columns: the primary email and the department.
Rule 2: Automate the process of updating users' organizational units when their department information changes.
Go to theRules page and click the New Rule button.
Select Manual trigger from the select a trigger screen.
Click Next.
On the Select an action screen, click the List users action.
Select Email and Department columns. Keep all other fields at their default settings, click Review.
Give the Rule name. Click Create. It was the first part of Rule 1.
Rule Triggering
Click on the Upload Icon to trigger the rule to download the CSV file.
Verifying Results
A notification will appear in the top right-hand corner. Click on it, then select Show All.
Additionally, access the Logs page from the left sidebar to discover logs of successful rule triggers.
Click here to Download the CSV file.
Proceed to create the second part of Rule 1.
Go to theRules page and click the New Rule button.
Select the Data uploaded trigger from the select a trigger screen.
Click on the upload box and upload the downloaded .CSV, wait for the CSV to be parsed.
In the Edit trigger screen, Leave all settings at their defaults.
Click Next.
On the Select an action screen, click on the If action.
Choose Department as the variable type and Text contains as the operator. Then, name your organizational unit (OU) as IT.
Click Add next action, then choose the Move user to organizational unit action.
Enter the Email in the User's primary email field and /Social Media into the New organizational unit field.
Navigate to the If action and add a Fallback branch. Then, click Add next action again, and select the Move user to organizational unit action. Repeat the same steps: Enter the Email in the User primary email field and /Social Media in the New organizational unit field. Then, click on Review to proceed.
Enter the Rule name, click Create.
Rule Triggering
Upload the same CSV file again and wait for it to finish uploading.
Check the Logs page to verify the execution of the rule.
Let's create the second rule
Go to theRules page and click the New Rule button.
Select the User department changed trigger from the select a trigger screen.
Leave the user primary field as default, then click Next to proceed.
On the Select an action screen, click the Get user info action.
Enter the User Primary email in the Primary email field.
Click Add next action.
Select the If action.
Again, select Department as the variable type and Text contains as the operator. Give a name for your organizational unit – Social Media.
Click Add next action. Select the Move organizational unit action.
Enter /Marketing in the Organizational unit path and /Tech Writing in the Move to field.
Next, navigate to the If action and add the Fallback branch. Click Add next action and then select the Move organizational unit action.
Enter /Marketing in the Organizational unit path and /Tech Writing in the Move to field. Click Review.
Give a Rule name. Click Create.
Rule Triggering
Before triggering the rule, update the user information in the Admin Console. Provide a name for the department and save the changes. After that, you can trigger the rule.
Verifying the Result
Once the rule is triggered successfully, you'll receive a notification confirming its execution. In the Action history, you'll see that the organizational unit has been moved from /Marketing to /Tech Writing. This rule automatically updates user information when there's a change in department.
Conclusion
Updating organizational units based on departments is a critical task that can have a profound impact on an organization's efficiency and effectiveness. By leveraging the power of xFanatical Foresight automation tool, this process becomes more streamlined, accurate, and scalable. Embrace the potential of automation and witness the transformation it brings to your organizational structure.
If you have yet to install Foresight, check out this quick start.
We use cookies to give you the best experience, as detailed in our privacy policy. By continuing to use this website, you consent to the use of cookies. Accept
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_ga
2 years
This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site’s analytics report. The cookies store information anonymously and assigns a randomly generated number to identify unique visitors. This cookie is installed the first time a visitor enters the website through a browser. When the visitor comes back to the website through the same browser, the cookie will consider them to be the same visitor. Only in the event that the visitor changes browser, will they be deemed to be a different visitor.
_gat_gtag-###
1 minute
This cookie is installed by Google Analytics. It is used to analyze visitor browsing habits, flow, source and other information.
_gid
1 day
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected includes the number of visitors, the source where they have come from, and the pages visited in an anonymous form.
CONSENT
2 years
YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
__Secure-1PAPISID
2 years
Used by for targeting purposes to build a profile of the website visitor's interests in order to show relevant & personalized Google advertising
__Secure-1PSID
2 years
Used by for targeting purposes to build a profile of the website visitor's interests in order to show relevant & personalized Google advertising.
__Secure-3PAPISID
2 years
Used by for targeting purposes to build a profile of the website visitor's interests in order to show relevant & personalized Google advertising.
__Secure-3PSID
2 years
Used by for targeting purposes to build a profile of the website visitor's interests in order to show relevant & personalized Google advertising.
_gcl_au
3 months
This cookie is set by Google Analytics to take information in advert clicks and store it in a 1st party cookie so that conversions can be attributed outside of the landing page.
1P_JAR
1 month
This cookie is installed by Google Ads. This cookie is used to collect site statistics and track conversion rates.
APISID
2 years
This cookie is used by Google to store user preferences and information while viewing Youtube videos on this site.
HSID
2 years
This cookie contains digitally signed and encrypted records of a user’s Google Account ID and most recent sign-in time. Google uses security cookies to authenticate users, prevent fraudulent use of login credentials, and protect user data from unauthorized parties.
LOGIN_INFO
2 years
This cookie is used by YouTube (Google) for storing user preferences and other unspecified purposes.
NID
6 months
NID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads.
PREF
2 years
This cookie is used by YouTube (Google) for storing user preferences and other unspecified purposes.
SID
2 years
This cookie contains digitally signed and encrypted records of a user’s Google Account ID and most recent sign-in time. Google uses security cookies to authenticate users, prevent fraudulent use of login credentials, and protect user data from unauthorized parties.
SIDCC
1 year
This cookie carries out information about how the end user uses the website and any advertising that the end user may have seen before visiting the said website.
SSID
2 years
This cookie is used to save the user's preferences and other information.
test_cookie
15 minutes
The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
VISITOR_INFO1_LIVE
6 months
A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSC
session
This cookie is used by YouTube to remember user input and associate a user’s actions. This cookie lasts for as long as the user keeps their browser open.
yt-remote-connected-devices
never
YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt-remote-device-id
never
YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt.innertube::nextId
never
This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
yt.innertube::requests
never
This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.