Before creating workspaces in your new ProjectPlace account, review and define the following settings:
Account administrators setup and manage the ProjectPlace account.
It is recommended to assign at least two account administrators as backup account administrators when the initial or primary account administrator is unavailable. Suitable account administrators may come from management, IT, project management, Human Resources, or the project office.
Account Owners can add Account Administrators and Account Co-owners.
There needs to be at least one Account co-owner to share the responsibility for the account. Additional information about account administration in ProjectPlace.
Account administrators can use the Automation tab to set up rules for workspace archiving based on the following criteria:
For more information on creating and managing account rules, see Manage Account Rules.
By default, all members in the account can start new workspaces. This allows each member to set up and organize their workspaces in a simple process without restrictions helping each user get the most out of using ProjectPlace. However, you can define who has the capability to start new workspaces or choose to prevent new users from creating workspaces, as described in the following procedure.
Settings for workspaces can be done from two places, under Workspaces tab > Settings icon > Settings for new workspaces option and Settings > Workspaces.
Under Workspaces tab > Settings icon > Settings for new workspaces option following settings can be made:
Under Settings > Workspaces following options can be made:
Prevent new users from creating workspaces
Prevent workspaces from being terminated
Custom message for terminating or archiving a workspace
Allow public sharing of workspace reports
NOTE
If you wish to change the default setting, an account administrator must write a request and send the request to the ProjectPlace contact listed in the overview in Account administration.
To define who should be allowed to start new workspaces:
NOTE
Enabling this may also cause integrations and automation rules that need to terminate workspaces to fail.
In the Allow public sharing of workspace reports section, specify whether you want to enable this functionality.
NOTE
Disabling this also deactivates existing public hyperlinks.
Click Save.
You can define the type of information displayed when a member tries to create a new workspace, but doesn't have the ability to create the new workspace. State who to contact within the organization, and what process to follow to create a new workspace. Be specific with your message and instructions to prevent frustration and help improve the process.
NOTE
By default, the message you create refers users to ProjectPlace support, so it is important to provide a personalized and detailed message so members in the account get the appropriate information.
To add information to users not allowed to start workspaces:
Associating a workspace with a department is helpful for internal invoicing purposes, and if desired, you can require that users select a department when creating a new workspace.
To define if users must select a department when creating a workspace:
Using the same template for new, similar workspaces helps members navigate through the new workspace. Members are familiar with the format of the new workspace when the workspace is based on a template that matches other workspaces they currently use. This is especially useful if the workspace an organization works from follows the same methodology or structure for every workspace within the organization.
NOTE
If the requirements of each workspace differs, the workspace creator should decide if the new workspace should be based on a template or not. Otherwise, a great deal of time and effort will go into changing/removing the predefined content for each workspace that has different requirements/uses.
To define if new workspaces must be based on a template:
NOTE
If you do not see a list of templates, it may indicate that you have not yet published any templates.
Collecting new workspaces in a portfolio makes it easier for account administrators to keep track of new workspaces being created in the account. The portfolio, and the workspaces within the portfolio, will only be visible for account administrators if no other portfolio owner or stakeholders are added.
To define a default portfolio for new workspaces:
NOTE
Regardless of the default setting, administrators for a specific workspace can choose if that workspace should be displayed in the portfolio or not.
The Settings Tab lets you make more global changes, compared with the micro-adjustments that the gear icon allows on some of the individual Tabs. Each dropdown item on the Settings Tab is discussed below in order of appearance.
The Enforced email domains section lets you see email domains that are used to automatically add users with that email domain as internal account members when they register their user account.
To set login and session settings:
NOTE
If the 'Keep me logged in' option is selected on the log-in screen, the user's session will be active for 14 days; otherwise, the user's session will be active for 2 hours before they are logged out. Select any value in this step to override. It applies to external users as well.
Minimum password requirements can be set for the account that all account members would be required to meet. You can also set a time interval before the password expires requiring the password to be updated. The password requirements apply to all members in the account, including external workspace members.
Try to keep the requirements as simple as possible, and as complex as necessary!
To define password requirements for the account:
NOTE
Users belonging to an account that has SSO configured will always log in using the login procedure required by the customer's Identity Provider.
NOTE
Password and two-step verification requirements can also be set on the workspace level. The strictest requirements will prevail when a user logs in to ProjectPlace.
For example:
Steve is a member of three workspaces in an account, with the following password requirements:
So, for Steve to be able to access all workspaces of which he is a member, his password needs to be a minimum of 8 characters, contain lower and upper case characters, include numbers, and expire every month. Steve will need to change his password at least once a month.
Account administrators can control which third-party document repositories they want to use within their organization.
NOTE
Documents from third-party services are stored in their respective repositories and are only referenced in the Documents tool, with the exception of documents from OneDrive and SharePoint.
In other words, document cannot be linked, but only be downloaded from OneDrive and Sharepoint.
OneDrive: allows only downloading files to workspace
Sharepoint: allows only downloading files to workspace
Any other third-party repository: enables linking files to workspace
To define third-party document repository settings:
A Robot is a special super user that allows programmatic access to an entire organizational account. It can create, read, update, and delete any information across all workspaces in the organizational account. This new feature can be accessed from the Account Administration > Settings dropdown. For more information, see this article.
Settings for workspaces can be done from two places, under Settings > Workspaces and Workspaces tab > Settings icon > Settings for new workspaces option.
Under Settings > Workspaces following options can be made:
Prevent new users from creating workspaces
Prevent workspaces from being terminated
Custom message for terminating or archiving a workspace
Allow public sharing of workspace reports
Under Workspaces tab > Settings icon > Settings for new workspaces option following settings can be made:
In addition to Defining who should be able to start new workspaces, the other Workspace Settings on this dropdown are covered in Manage Workspaces in the Account under Selecting Workspace Settings.
Account administrators can create custom fields that will be published to all workspaces. This will allow workspace managers to add values to custom fields in a workspace and help stakeholders to have more detailed information about every workspace in the account.
The account administrator will also be able to view and edit the custom values that have been published to the workspace by selecting a workspace in Account administration > Workspaces tab. The detail pane of a workspace will show the custom fields.
The workspace owner/administrator can view and edit the custom values that have been added to the workspace.
NOTE
If custom fields have been added in Account administration they will be presented below the default fields. The custom values will not be mixed with the default fields since only the default fields are localized.
Third party application developers and ProjectPlace customers can use ProjectPlace Application Programming Interfaces (APIs) to create applications that access information in ProjectPlace workspaces and present it in new ways.
Applications that use the ProjectPlace APIs fully respect the security and authorization mechanisms you are already familiar with in ProjectPlace. For example, a workspace member using a third party application will never have access to more information than what is already available to the member.
To define third-party software settings:
We have added Settings for the Workload tool in Account administration. In the Settings window the account administrator will be able to set:
To set Workload settings:
If all users are connected to a department, you can get an overview to divide the cost of ProjectPlace between departments. Account administrators can always change the department for a user.
To set a department for users:
Add a department called Others for account members that do not know their department or do not find a matching department. It is then easy for the account administrators to find those users and assign them to the correct department.