4 - Import Permissions for Watch Student Feature

After the SSP-Platform source has been pulled into the local repository, the following import will add the appropriate permissions for the Coach and Manager roles to enable the Watch Student feature.

SSP_CONFIGDIR=</path/to/your/config/dir> ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_entities/patches-SSP-2-6-0/SSP-770 data-import

5 - Import Permissions for Bulk Action Features

After the SSP-Platform source has been pulled into the local repository, the following import will add the appropriate permissions for the Coach, Manager and Administrator roles to execute Bulk Actions from the Caseload and Search Results

SSP_CONFIGDIR=</path/to/your/config/dir> ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_entities/patches-SSP-2-6-0/SSP-2086 data-import

6 - New permissions and functionality were created to remove the Main Tool from individual users or groups/role (added in v2.5.2)

The intent of this feature is to remove the display of protected information from users who should not have access.  For example, the application can be configured such that faculty members who do not need to view academic history for any student will not have the Main Tool available in the UI.  Instructions to manage the permissions are described in the User Guide. Before you'll be able to manage those permissions, though, you need to run the following command from within your SSP-Platform source code checkout (only necessary for an upgrade; fresh installs will execute this file automatically):

SSP_CONFIGDIR=</path/to/your/config/dir> ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_entities/patches-SSP-2-5-2/SSP-2631 data-import

7 - New permissions and functionality to display Student Risk Indicators on the Main Tool (added in v2.6.0)

The intent of this feature is to display student risk factors based on data loaded into the external database table.  SSP will display the indicators defined a active in administration.  Before you'll be able to manage those permissions, though, you need to run the following command from within your SSP-Platform source code checkout (only necessary for an upgrade; fresh installs will execute this file automatically):

DM: Don't do this! Current thinking is that this permission is going to be backed out before the 2.6.0 GA and we have no good way of doing that in beta field deployments.

SSP_CONFIGDIR=/path/to/your/config/dir ant -Dmaven.test.skip=true -Ddir=uportal-war/src/main/data/ssp_entities/patches-SSP-2-6-0/SSP-2899/permission_set data-import

SSP v2.6.0 JIRA Issues