This article shows you how to modify Default Folders, Sign-Up as an Organization, and adjust Login Profiles.
This article shows you how to make administrative adjustments to existing Accounts, specifically the Default Folder configuration and Profile Login references. Results will be used in subsequent Sharing/ Managing Data Walkthroughs.
This article uses the previously-created Test Organization and member Test Accounts from the Walkthrough, Migrate To An Organization and subsequent Provisioning in the Walkthrough, Provision, Validate, Dismiss. This includes the following, based on our use of the source email address email@example.com, enumerated with related resources names:
- Organization Administrator -> firstname.lastname@example.org, Default Folder = C:\TestData
- Non-Privileged User 1-> email@example.com, Default Folder = C:\TestDataO1U1
- Non-Privileged User 3 -> firstname.lastname@example.org, Default Folder = C:\TestDataO1U3
Though you can use Production Accounts, we recommend the use of Test Accounts due to the way content is stored, shared, and accessed.
We encourage the use of similar naming conventions, which to this point in ordered review hasn't been as much a hassle as further activity would expose. For this reason, we will make associated adjustments to the Profiles to simplify matters going forward.
Define/ Change Default Folders for Test Accounts
Previous Walkthroughs didn't provide explicit guidance for 1st Time Use of the Non-Privileged Accounts we'll use here, so our first activities align Default Folder configuration with the associations given above.
Note that we'll offer guidance for both possible cases - 1) You independently performed Login for one or both Non-Privileged Accounts and proceeded through the 1st Time Use prompt(s), and 2) You have not yet logged in to one or both Accounts.
Let's start with the scenario depicting 1st Login of a Non-Privileged Account after Validate execution.
STEP 1: Log In to your User 1 Test Account, which for us is email@example.com.
STEP 2: If you haven't logged into the Account since Validation, you'll be prompted to configure your Default Folder (steps to change an already-configured Default Folder follow below):
STEP 3: Choose Yes, then create and assign a unique folder for this Account - we used C:\TestDataO1U1 to reflect the Organization and Account/ User since this will serve our needs going forward.
Let's do the same for the User 3 Test Account, but in this case we'll change an undesired setting.
STEP 4: Refresh Login (using the context menu available from the notification tray's SSProtect icon), and from the Login dialog's Profile dropdown, choose your User 3 Test Account - for us this is firstname.lastname@example.org. Enter the Account's Password then Log In to SSProtect.
If you've already configured a Default Folder, skip to STEP 6, else:
STEP 5: When prompted to configure your Default Folder, navigate to C:\TestData and choose this location. We'll change it below.
STEP 6: From the context menu, choose Managed Files/ Restore to display the Managed Hostlist:
STEP 7: Click Adjust... in the lower right portion of the dialog, next to your Default Folder. When you do this, SSProtect will Prompt you to explain the reality of this procedure (more below):
Your Default Folder is more than the default target for storing files, such as Usage Reports and Key Export results, it also serves as a point of indirection when working on multiple host computers.
In short, you set a Default Folder for each host computer to which you Remote Deploy your Profile, and any subsequent Restore operation for items in the Default Folder maps to the host-specific setting rather than to the literal location (using Replicate logic as a fallback when the literal location cannot be created).
We'll cover these details (and related issues) in subsequent Walkthroughs. For now, let's get back to adjusting the Default Folder for User 3:
STEP 8: Choose OK then create a Default Folder specific to this Account - we used C:\TestDataO1U3 to follow a simple convention that will facilitate our forward efforts. When the change is applied, SSProtect will return to the Login dialog.
Create a New Organization With Sign-Up
Let's use Sign-Up to create an Organization, which is more common than creating an Individual Account before Migrating to an Organization, as described in prior Walkthroughs, Provision Test Accounts and, Migrate to an Organization.
STEP 9: From the Login dialog, choose Create New... from Profiles and enter the Email Address for the Administrator of a second SSProtect Organization we'll create. We recommend the use of a Gmail alias and, consistent with existing Walkthroughs, use for our purposes the Organization named gmail-definisec_t2 with the email alias email@example.com:
STEP 10: Enter the Organization Name using a format suitable for Auto-Approval (previously discussed). Auto-Approval naming uses the domain of the email address as the prefix, then your chosen (Org or Team) name i.e. domain-<OrgTeamName>. Choose Create. This will be your 2nd Organization's Administrator.
STEP 11: When prompted to set your Default Folder, choose Yes then create and use C:\TestData2.
STEP 12: When prompted to Export Keys, choose Yes and follow the procedure as before. You will be returned to the Login dialog to continue - enter your new Account's Password to complete the operation.
Rename Profiles to Align Ongoing Proceedings
We can use Profiles for a level of indirection in subsequent guidance and text, eliminating the need to constantly qualify which Organization/ Account we're using and refer simply to the Profile name.
STEP 13: From the notification panel, right-click the SSProtect icon and choose Refresh Login..., then from the resulting Login dialog, choose Advanced:
STEP 14: Choose Profiles to edit your existing Profiles:
STEP 15: Choose from the Profile dropdown the first Account in the list below, then Edit... and for the New Name use the list's Profile before choosing Save. then repeat for all Accounts in the list. Don't use Done to exit the Profiles dialog just yet - we'll do one more thing, below, before we continue.
Despite the lack of creativity, we'll use the following references going forward:
- Organization 1 Administrator -> firstname.lastname@example.org -> Profile=Org1_Admin
- Organization 1 User 1 -> email@example.com -> Profile=Org1_User1
- Organization 1 User 3 -> firstname.lastname@example.org -> Profile=Org1_User3
- Organization 2 Administrator -> email@example.com -> Profile=Org2_Admin
Note that the default Profile naming convention is different - <Organization Name> (<email_address>), though for our purposes we're using the modified convention for brevity (and because we can).
Delete The Unused Profile
Before dismissing the Profiles dialog, check to see if you still have the, "dangling" reference to an Account we attempted to Create by joining an Organization, subsequently Dismissed:
- Organization 1 User 2 -> firstname.lastname@example.org
STEP 16: If present, because it's no longer useful, using the Profile dropbdown, select the noted dangling Profile and choose Edit... then Delete and acknowledge the confirmation prompt. Choose Done to return to the Login dialog.
Note that the Profile Delete operation does not remove the Account, it only removes Account data stored on your local computer. We will revisit this when we turn our attention to Remote Profile Deployment in our Response/ Recovery series of Walkthroughs.
SSProtect uses a 1st Time Use progression to configure Account resources, though in almost every situation you can specialize and/ or change settings later - as we have shown with respect to Default Folder configuration.
Profiles simplify the complexity of worrying about Account email Usernames, and we'll use the most recent changes in ongoing Walkthrough references as it would otherwise be a little too confusing.
This article was updated w/ v10.7.1 of the :Foundation Client