Project - Workspace
Project workspaces provide an online area to facilitate collaboration within delivery teams. Workspaces let you see your team members, coordinate and prioritize issues related to project delivery, share documents, and view invoicing data. Your clients also have the ability to login and collaborate with your team. This tab manages permissions and settings in a project workspace. To view project workspaces in action, see the Project Workspaces documentation.
In the Collaboration and Project Workspaces webinar we demonstrate using Projector’s project workspaces for project collaboration.
Permissions and Settings
The following people can make changes on this tab:
- Anyone with the cost center permission Maintain Projects and Engagements
- Engagement manager, Project manager, and Can Act as PM users when the stage permission Configure Workspaces is enabled
For team members to access Project Workspaces the following is required:
- Enable Project Workspace checkbox ticked on Project - Workflows
- Users with permissions can access workspaces enabled for current Project Stage
- View access or greater granted on the Access section of this page
For client users to access Project Workspaces the following is required:
- Enable Project Workspace checkbox ticked on the Project - Workflows
- Client Can Login to project workspace enabled for current Project Stage
- View access or greater granted on the Access section of this page
- Client user added on this page
Default workspace permissions are determined by Engagement Type.
Permission sets managed through the Permission Sets Editor.
Project Workspace Access
Control who can access your project workspace and what they can view. For each category of users, select an appropriate permission set.
Permissions
Your users are categorized into the following groups. The table below explains who is a part of each group.
Relationship to Project | Description |
---|---|
Engagement Manager | Defined on the Engagement - Setup Engagement |
Project Management Team | Defined on the Project - Setup Project. Includes anyone who can Act as PM |
Resource Assigned to a Role (Non-limited User) | Any resource who is currently booked to the project. |
Resource Assigned to a Role (Limited User) | Any resource who is currently booked to the project and is limited |
Resource Not Assigned to a Role (Non-limited User) | Any active resource in your organization. Does not require any special permissions (view project, etc). |
Resource Not Assigned to a Role (Limited User) | This option was included for completeness, but is effectively non-functional. Limited users are excluded from viewing projects they don't have a role on. As of this time, that situation does not occur. |
Client User | Any user with the Client flag set on their user profile. Client users are logins created for your clients. This allows them to log into Projector and collaborate with your team and view their invoices. |
User with Cost Center Permission | Users with the cost center permission Access Project Workspaces for this project's cost center |
Permission Sets
A permission set grants view or edit access to each of the four section in a workspace - Home, Issues, Invoices, and Documents. Click to show the access legend.
Use the dropdown box to set access for each group of users.
Client Users
Add individual users and grant them access to the workspace.
Field | Description |
---|---|
Name | Username |
Client | From Clients. Empty for non-client users. |
Allow access | This read-only field is here to confuse you |
Permission Set | Which permission set should this client user get? |
How come I can add any user I want? If client users are associated with a specific client through the user editor, why isn't the clients tab prepopulated?
The answer to both questions is the same. We allow any client to be added in case you are using client levels. In these cases you may want a parent client user to access child client projects. This is also the reason we don't prepopulate the list.
Project Home Tab Configuration
The project home tab typically shows a short message about what this project is and a logo. Often the logo used is the client's. This gives a personalized feel for clients that do login to review issues or access their invoices.
Issues Tab Configuration
Configure your issue categories and statuses. See Issues to see how they are used.
Issue Categories
Column | Description |
---|---|
Name | Your users will choose this name when assigning a category to an issue. |
Inactive | An inactive issue is unavailable for new issues, or for moving a current issue to it. Existing issues remain unaffected. |
Delete | Remove the category. If there are any existing issues using this category, then it cannot be deleted. Mark inactive instead. If you really need to delete the category then you should log into the project workspace and change all existing issues to a new category. Then delete. |
Issue Statuses
Then define your Issue Statuses.
Column | Description |
---|---|
Status Name | Set status name |
Closed | Closed statuses are hidden in default views |
Inactive | Do not let new issues or existing issues enter this status. Existing issues will continue to have this status |
Delete | Remove the status. If there are any existing issues using this status, then it cannot be deleted. Mark inactive instead. If you really need to delete the status then you should log into the project workspace and change all existing statuses. Then delete. |