- Self-Service Permissions
- Permissions Requiring a Request to Terra Dotta
- Permissions Not Granted to Clients
- Email Tests
- Login Attempts
- Sent Email
- System Errors
- SIS Refresh
- Merge User
- Scrub Application
- Scrub Program
- Scrub App Cycle
- Convert User
- Edit User
- SIS/HR Tests
- Text Interface
- Cross-Site Scripting
Let's take a look at each of these permissions in more detail:
This permission lists your current system contact email addresses and allows an admin to initiate test emails to those addresses to ensure system emails are being delivered as expected.
This permission allows an admin to see a record of all attempted logins to their site and provides details about the identity of the person attempting to log in, when they made the attempt, and whether or not the attempt was successful.
This permission provides a log of every system-generated email delivered through the site in the past 60 days. Because confidential topics may be discussed via email, it is recommended to give access to the Sent Email log only to those who need it.
This permission provides a detailed report of errors generated in your Terra Dotta site.
Allows a user to access detailed SIS refresh logs and manually initiate a SIS refresh for the site (used only on sites integrated with a SIS/HR directory).
For more detailed information, refer to the Getting Started with the SIS Refresh Knowledgebase (KB) article.
Gives the admin the ability to merge two user identities on the site and deactivate unneeded accounts.
For more detailed information, refer to the Resolving Duplicate Accounts and Profiles in Terra Dotta KB article.
This permission allows an admin to completely (and irreversibly!) delete a user's application/record.
Important Note: It is not recommended to scrub applications from your production site as this permanently and irrevocably removes the applications from your database. Suggested alternatives are to move unwanted applications into the withdrawn status or create a status alias for withdrawn that identifies testing/bogus applications.
To scrub an application:
1) Navigate to Maintenance > Scrub Application. Locate your desired application using the options provided and click "Search".
- Providing Material notes
- Application tags
- Alumni settings
- Application comments
- Application dates (risk)
- Application locations (risk)
- Application materials
- Application reviews
- Assessment responses
- Assessment scores
- Journal entries
- Learning content
- Credit transfers
- Application documents
- Status history
- Student parameters
- Questionnaire responses
- Recommendation responses
- Recommendation requests
- Root application record
The following information is not scrubbed but is instead only dereferenced:
- Signed content of signature documents (actual CLOB record of content)
- Legacy saved signature document content data (before CLOB data was used)
- History log entries
- Journal images
- Uploaded binary files (Documents tab)
- Decision letters
The following data is not scrubbed because it is a part of the applicant's profile and not the application itself. It may remain relevant and necessary to retain when scrubbing an application:
- Core data fields
- Applicant parameter data (SIS and Non-SIS)
- Applicant parameter data history
- Address information (SIS and Non-SIS)
- Profile image
- Profile bio
- Saved programs
- Profile comments
- Profile history log
- CC/SMS email addresses
This permission allows an admin to completely (and irreversibly!) delete a program from the site.
Scrub App Cycle
This permission allows an admin to completely (and irreversibly) remove an unused application cycle. Application cycles with associated applications cannot be deleted as those applications would become orphaned due to missing data. Therefore, you would need to scrub associated applications before being able to scrub the app cycle.
To scrub an application cycle:
1) Navigate to Maintenance > Scrub App Cycle. A list of all app cycles will appear in a table with several column headers, including Term, Year, Active, Dual Year Term, and # of Applications. Only app cycles for which there are no current applications will display a "Remove" button in the first column of the table.
2) Click "Remove" to proceed with scrubbing your app cycle. A dialogue box will appear asking you to reconfirm your decision.
This permission allows an administrator to find a non-SCL user and convert them to an SCL-user or to import a batch of users to convert.
Important Note: Core data fields for integrated users are not editable in this interface. Edits for internal, integrated users must be made in your institution's student information system (SIS) or HR directory before being pushed to Terra Dotta through your integration.
This permission permits an admin to edit the core data fields (username, name, internal/external, integrated/non-integrated, email, DOB, gender, confidentiality indicator) of an external user's account and reset their password and security credentials.
In the search field provided in Maintenance > Edit User, enter the name or email address of the applicant for whom you need to make an edit and click "Search". From the list of records that appear, select the radio button next to the applicant's name and click "Next".
This permission alows an admin to perform search tests of integrated SIS and HR systems to ensure user data is being imported as expected.
This permission allows an admin to edit specific default text coded into the website.
For more detailed information, refer to the Text Interface Customization KB article.
Cross-site Scripting (XSS) Protection
This permission, a series of two settings located under Maintenance > Environment Settings, permits an admin to override Terra Dotta's native cross-scripting protections when editing in a WYSIWYG editor on the site.
An example is a pop-up prompt asking the user for private information and then sending the information to another site or database.
Terra Dotta provides a security permission to waive all content restrictions to either individual users or groups, allowing users with this permission to create rich/dynamic content such as embedded videos. The permission is:
Maintenance: allow posting of blocked script elements in WYSIWYG content (override XSS blocking).
Users with this permission will be exempt from the XSS protection measures when using a WYSIWYG editor. Note: Any content added by a user with this permission will be rendered inoperable again if that content is edited and saved by a user without this permission.
Hosted Terra Dotta clients can have their Primary Admin User open a support request to ask for this permission for the admin users who need it.
Permissions Requiring a Request to Terra Dotta
The Data Import/Export permission can only be granted to administrators by a member of Terra Dotta's Support staff. Please open a case with Terra Dotta Support to request a user be granted this Maintenance permission.
For more detailed information, refer to the Data Import/Export Utilities KB article.
- Unrestricted Access
- File/Folder Check*
- Task Scheduler
- SIS/HR mappings*
- Environment Settings
- Settings Inspector
- Version Info*
- Task Logs*
- ColdFusion Logs
*Permissions denoted with an asterisk (*) were available for assignment on client sites prior to the Terra Dotta Study Abroad 19.0 release. If one of these permissions was assigned to you prior to the 19.0 release, it will not be removed automatically. However, you will not be able to assign it to new users and, if it were to be removed from your account, you will not be able to have it reassigned to you.