#User Permissions Grid

This application allows Subscription Admin to list all the users in a subscription and view / download its workspace and project permissions.

You will be able to select one or more workspaces to list its users and permissions.

####Steps to install the Application

1. On your dashboard, click on the gear to add an app.
2. Choose "Custom HTML" from the App Catalog. Add the app.
3. Paste the code to HTML text area from the link - https://github.com/RallyTechServices/user-permissions-grid/blob/master/deploy/App.txt
4. Click Save.

####Steps to get started:

1. Once the application is installed, you will be able to choose the workspaces by clicking "Select Workspaces..".
2. If you do not choose a workspace, the application will list all the permissions for the current workspace.
3. Click update. Please note that. This may take long time to load the grid based on the size of the subscription and number of workspaces selected.
4. Once the grid is loaded, click on next pages to view the grid.
5. Click on "Download CSV" to download all the records in a CSV file.

Development Notes

First Load

If you've just downloaded this from github and you want to do development, you're going to need to have these installed:

• node.js
• grunt-cli
• grunt-init

Since you're getting this from github, we assume you have the command line version of git also installed. If not, go get git.

If you have those three installed, just type this in the root directory here to get set up to develop:

npm install

Structure

• src/javascript: All the JS files saved here will be compiled into the target html file
• src/style: All of the stylesheets saved here will be compiled into the target html file
• test/fast: Fast jasmine tests go here. There should also be a helper file that is loaded first for creating mocks and doing other shortcuts (fastHelper.js) Tests should be in a file named -spec.js
• test/slow: Slow jasmine tests go here. There should also be a helper file that is loaded first for creating mocks and doing other shortcuts (slowHelper.js) Tests should be in a file named -spec.js
• templates: This is where templates that are used to create the production and debug html files live. The advantage of using these templates is that you can configure the behavior of the html around the JS.
• config.json: This file contains the configuration settings necessary to create the debug and production html files. Server is only used for debug, name, className and sdk are used for both.
• package.json: This file lists the dependencies for grunt
• auth.json: This file should NOT be checked in. Create this to run the slow test specs. It should look like: { "username":"you@company.com", "password":"secret" }

Usage of the grunt file

####Tasks

grunt debug

Use grunt debug to create the debug html file. You only need to run this when you have added new files to the src directories.

grunt build

Use grunt build to create the production html file. We still have to copy the html file to a panel to test.

grunt test-fast

Use grunt test-fast to run the Jasmine tests in the fast directory. Typically, the tests in the fast directory are more pure unit tests and do not need to connect to Rally.

grunt test-slow

Use grunt test-slow to run the Jasmine tests in the slow directory. Typically, the tests in the slow directory are more like integration tests in that they require connecting to Rally and interacting with data.