{"id":5281,"date":"2022-11-04T13:05:43","date_gmt":"2022-11-04T13:05:43","guid":{"rendered":"https:\/\/gatlabs.com\/knowledge\/?post_type=docs&p=5281"},"modified":"2022-11-11T14:22:57","modified_gmt":"2022-11-11T14:22:57","password":"","slug":"setting-users-custom-attributes-with-gat-flow","status":"publish","type":"docs","link":"https:\/\/gatlabs.com\/knowledge\/tech-tips\/setting-users-custom-attributes-with-gat-flow\/","title":{"rendered":"Setting Users’ Custom Attributes with GAT Flow"},"content":{"rendered":"

GAT Flow <\/a>addresses the lack of criteria for categorization <\/span>by allowing the Google Workspace<\/a> Admins to create their own users’ custom attributes.<\/span><\/p>\n

Many companies and schools may have certain criteria for categorizing employees, managers, teachers, and students.<\/p>\n

Google Admin Console has many options to allow an admin to input user data so that it can be manipulated in certain ways.<\/p>\n

However, Google Admin Console data fields are set in stone, and many of these categories fall short of what is required when an Admin wants to enter a specific characteristic that might only be relevant to their organization.<\/p>\n

Below we explain how to solve this problem using GAT Flow.<\/p>\n

How to use the custom attributes in the signature<\/h2>\n

One use case for the users’ custom attributes might be in setting the user’s signature.<\/a><\/p>\n

If you would like to add specific information to the users’ signature, for example, their location, you can add it to the signature if that data has been entered in the Users<\/strong>\u00a0section of GAT Flow.<\/p>\n

Step 1.<\/h3>\n

To begin, Create a workflow<\/strong>, and set the type to Modify<\/strong>.\u00a0Click Next<\/strong>\u00a0to continue.<\/p>\n

\"Step<\/p>\n

Step 2.<\/h3>\n

On the Search for user<\/strong> screen, select the users you want the workflow to run on, and click Proceed to actions<\/strong>.<\/p>\n

\"Step<\/p>\n

Step 3.<\/h3>\n

On the Choose actions<\/strong> screen, for this example, we will choose to Add an action<\/strong> by using the (+) button<\/strong> on the left.<\/p>\n

\"Step<\/p>\n

Step 4.<\/h3>\n

Navigate to Set email signature<\/strong>.<\/p>\n

\"Step<\/p>\n

Step 5.<\/h3>\n

Here you can select custom attributes you have previously created in the user’s signature. Simply click on the attribute in the top pane and it will appear in the bottom pane.<\/p>\n

\"Step<\/p>\n

Step 6.<\/h3>\n

When you are finished editing the signature, click Send approval request<\/strong>\u00a0to finish.<\/p>\n

Conditional Workflows with Custom Attributes<\/h2>\n

You can also use these custom attributes in a conditional workflow.<\/p>\n

Using the same custom attribute, we will create a workflow that will only be triggered if a user is in a specific part of the world.<\/p>\n

In our hypothetical scenario, there are folders that our US-based accountants need to have in their myDrive. Though if the accounts team members are not from the US, they should not have the folder as it doesn’t apply to them.<\/p>\n

To automate this process, we will start the workflow after moving the user to the Accounts Department OU. And have GAT Flow decide if the user needs the folder.<\/p>\n

Step 1.<\/h3>\n

To begin, create a workflow of any type. For this example, we are going to make use of some automation by creating an event workflow.<\/p>\n

Step 2.<\/h3>\n

Choose Event workflow<\/strong> from the left-hand side and click Create workflow<\/strong> on the top right-hand side.<\/p>\n

Name the workflow and use Modify <\/strong>for the Type of workflow<\/strong>.<\/p>\n

For the Event, <\/strong>field select Start when a user is moved to an Org Unit<\/strong>.<\/p>\n

As we are going to have this run on the Accounts Department, select that in the Ous<\/strong> field.<\/p>\n

Switch on the Conditional flow<\/strong>\u00a0slider, and click Next<\/strong>.<\/p>\n

\"Step<\/strong><\/p>\n

Step 3.<\/h3>\n

On the next screen, select the Add condition<\/strong> button from the start menu. In the box that appears, select the Advanced<\/strong> dropdown menu, scroll to the bottom and select the Employee data – Location<\/strong>.<\/p>\n

The next option is Equal<\/strong> meaning ‘exactly the same’, so the Employee data – Location will need to be ‘exactly the same’ as what you entered in the field below.<\/p>\n

For this use case, we will leave it as is.<\/p>\n

In the bottom field, we will enter US<\/strong>.<\/p>\n

NOTE:<\/strong> If an employee’s<\/em> data had ‘USA’ entered for location data, GAT Flow would not see this as equal, as ‘US’ and ‘USA’ are not exactly the same. If we wanted this workflow to run on the users from the USA, we could select Starts with <\/strong>instead of Equal<\/strong> to select users with USA entered in their location data.<\/em><\/p>\n

Step 4.<\/h3>\n

On the right-hand side of the conditional box, select the option Add action in case of yes ><\/strong> Copy folder to selected user(s)<\/strong>.<\/p>\n

Choose the user that has the folder, and then select the folder(s) you want to copy. In this case, we will select all folders.<\/p>\n

\"Step<\/p>\n

On the Copy folder to selected user(s)<\/strong> box, click the down arrow to End graph here<\/strong> and end the Yes <\/strong>side of the condition.<\/p>\n

We aren’t going to do anything within this workflow if the users are not from the US. On the No <\/strong>side of the conditional box, select the down arrow to End graph here<\/strong>.<\/p>\n

On the left side of the workflow, if the user is not in a specific location, we will choose to do nothing, so select\u00a0End graph here<\/strong>.<\/p>\n

Step 5.<\/h3>\n

Now click Send approval request<\/strong>\u00a0to finish.<\/p>\n

Result<\/h3>\n

We can also check what happens when this workflow is triggered.<\/p>\n

We created the workflow to move a couple of users to the Accounts Department OU. One user is based in the US and the other is not. The screenshot below indicates that the operation was completed successfully and both users moved to the Accounts Department OU.<\/p>\n

\"Final<\/p>\n

We can see on the next screenshot below that our event workflow has triggered, though we can only see for one of the users.<\/p>\n

\"Final<\/p>\n

Clicking the number 1<\/strong> in the Done<\/strong> column shows more details about what happened.<\/p>\n

And finally, in the screenshot below, we can see on which of the two users the workflow was run and that the folders were successfully copied.<\/p>\n

In moving two users to the Accounts Department, one based in the US and one not, we can see that the event workflow worked as expected and copied the folders to that user only.<\/p>\n

\"Final<\/p>\n

Related posts<\/h2>\n