ÃÛ¶¹ÊÓƵ

Transcript

Welcome to the step-by-step walkthrough of how to configure Target Workspace in the ÃÛ¶¹ÊÓƵ AdminConsole. By the end of this video, you’ll learn how to access the ÃÛ¶¹ÊÓƵ AdminConsole from within the ÃÛ¶¹ÊÓƵ target interface. How to configure target workspace from within the ÃÛ¶¹ÊÓƵ AdminConsole, including how to add users to workspaces as well as how to add properties to workspaces. And finally, how to understand the concept of default workspaces. By creating workspaces for your organization, you will be able to organize and group together common sets of properties, audiences, offers, and activities so that only a specific set of users may gain access to them. Let’s get started with understanding the interaction between ÃÛ¶¹ÊÓƵ Target’s interface and that of the ÃÛ¶¹ÊÓƵ AdminConsole. There are three ways to access the AdminConsole from the Target interface. The first access option exists in this gear icon in the top right hand side of your screen and the second two options live within the setup menu with the AdminConsole access points under users and properties. Meaning that no matter where you are in ÃÛ¶¹ÊÓƵ Target’s interface, the AdminConsole is just one click away. Now that we’ve reviewed the three points of access to the ÃÛ¶¹ÊÓƵ AdminConsole from Target, let’s jump into how and why to configure Target workspaces. So far in the process, you have determined the domains, apps, and workflows that certain users within your organization will need to be given access to or will need to be restricted from. You’ve identified each component’s corresponding channel, implemented its property token, and are now looking to group these properties into workspaces along with the users who will need access to them. One of the most common use cases amongst our customers is to split workspaces by geographic region so that teams have their own separate space where their relevant properties, activities, audiences, and offers live. In order to set up a configuration like this, we can create a workspace for each of our regional teams. Let’s start with an America’s workspace where users on the company’s North and South American teams can access and collaborate on target activities relevant to their organizational goals. From Target, use one of the three methods we covered earlier to access the AdminConsole, where you’ll instantly be able to view all workspaces associated with your organization. If you have yet to create any workspaces thus far, you will only see one default workspace listed. The purpose of which we will discuss shortly. To configure my America’s workspace, I will click on the blue new profile button above into the right of the product profiles list. On the next screen, enter the name of your workspace. I also have the option of writing out a brief description in the field below the profile name so that users added to this workspace can know at a glance what it contains. Once you’ve completed this step, make sure to hit the blue done button below.

From here, you’ll be directed back to the AdminConsole product profile list. Except now, in addition to the default workspace, you will also see your newly configured America’s workspace. Remember however, that you are currently in the AdminConsole. In order to access this workspace from your Target interface, you’ll first need to add yourself to it as a user. In order to add myself or other users from the North and South American teams to this workspace, I’ll simply click on the new workspace as it appears in the product profile list in the AdminConsole, and then on the blue ad users button that appears on the next page. If you or the user you are trying to add have already been configured as users in your organization, you should be able to search by name or email address. Once you’ve identified the users that you’d like to add to this workspace, select their name from the dropdown and then be sure to hit the blue save button on the bottom right of your screen. You’ll receive a message in a green popup at the bottom of your screen, confirming the addition of a user. You’ll also notice that from this user’s tab within your new workspace, you can set the roles associated with each user, observer, editor, or approver. You can take the same steps to add other users and roles to this product profile. For example, for the America’s workspace, you’ll want to add those users who work on the teams in the Americas. If you need to add a user who is not previously added to your organization, take the same steps and that user will be invited via email with an ÃÛ¶¹ÊÓƵ id. Now, when I go to ÃÛ¶¹ÊÓƵ Target, I will be able to see the America’s workspace listed as an option in the dropdown, meaning that it will only appear in Target to those users who have been given access to it. If you have any trouble viewing a new workspace in Target, be sure to either refresh your browser or sign out and sign back in. Now that you have configured your Target workspaces within the ÃÛ¶¹ÊÓƵ AdminConsole and have added the right users, it’s now time to add the appropriate properties to each as well. In order to add specific properties to your newly created product profiles, simply click on the name of the product profile in the list within the products tab. From there, navigate to the permissions tab where you will see a list of property channel types indicating in the right most column, the number of existing properties in your organization that belong to each. So, for example, when I click on the web channel type, I can choose which web property I’d like to include in my America’s workspace. I’ll click on the plus sign next to the property name, ensure that this property moves to the included column on the right, and confirm the action by hitting the blue save button below. Since I am creating this workspace for teams within the Americas, I will only include those properties that this team will need access to, namely those that are based in either North or South America. From here, I will continue adding the appropriate properties from the other channel types to the Americas workspace so that my Americas teams have access to the properties they work most closely with. While these specific workspaces serve to contain, organize, and streamline users activities on Target, whether it be by region, internal organization, specialty, or anything else, default workspaces function as a type of catchall environment where anyone who has access to Target will have access to that organization’s default workspace. It is up to the administrator to restrict users access to the default workspace, and instead assign those users to the workspace that specifically concerns their work. For more on target workspaces, check out our ÃÛ¶¹ÊÓƵ Target product documentation or visit Target’s online community at forums.adobe.com. Thank you.