Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

 Is your application accessed through a browser?

Is your service accessed through a browser?

Yes. With any of Edge, Firefox, Chrome, Safari or Opera.

More information: https://commonplace.atlassian.net/l/cp/4fQTBENt

 Which browsers does your application support?

Which browsers does your application support?

Edge, Firefox, Chrome, Safari or Opera.

More information: https://commonplace.atlassian.net/l/cp/y8X2D4Xp

 Is there an application that users install to use your service?

Is there an application that users install to use your service?

No.

More information: https://commonplace.atlassian.net/l/cp/mfX1xgxH

 Which operating systems does your service work with?

Which operating systems does your service work with?

Windows, MacOS, Windows Phone, Android, iOS, Linux / Unix

More information: https://commonplace.atlassian.net/l/cp/18u9UNLa

 Has your service been designed to work on mobile devices?

Has your service been designed to work on mobile devices?

Yes. The respondent parts of our platform are designed and built for mobile first. The editor provides a mobile preview to help our customers optimise their content for mobile users, which make up 73% of visitors.

More information: https://commonplace.atlassian.net/l/cp/1vAodCyX

 What integrations to external services do you provide?

What integrations to external services do you provide?

Salesforce CRM

Hubspot CRM

ESRI mapping

Zoom webinars

More information: https://commonplace.atlassian.net/l/cp/024GAXPf

 What are the user roles available?

What are the user roles available?

The following roles are available for customer users, who access the platform with a username and password:

1. Admin:

  • Can add, edit and revoke user accesses

  • Have access to all communications and all data

  • Can edit the project or programme settings

  • Can change branding elements

  • Can create and send communications

2. Surveyor:

  • Can log survey answers from the survey pages 

  • Cannot edit, create or delete content nor send communications

  • Cannot manage other user roles

3. Tester:

This role is suited for people working on your user website before launch. A tester cannot access the dashboard or manage other user roles

They can:

  • Create, edit and delete content and pages

  • Can change branding elements

4. Communications manager: 

  • Can create, edit and delete news and timelines components only

  • Can change branding elements

  • Can group and email respondents and contributions in the dashboard

  • Can manage other user roles

5. Stakeholder:

This role is suited for individuals who have been asked to take part in your consultation as members of a closed audience.

Respondent users create an account upon submission of their first contribution, if they decided to provide an email address (which is optional). Upon submission, if they did provide an email address, they will instantly receive a verification email. Users can later log in to their platform profile page by a password-less magic link request, which is sent to their email address. Respondent users have a status:

Pending - email verification was not completed, their contribution will not be made public

Confirmed - email verification was completed successfully, their contribution will be available publicly

Respondents who do not provide an email address do not have an account created in the Commonplace application.

More information: https://commonplace.atlassian.net/l/cp/K12wrGLb

 How is account recovery and lock out managed for Commonplace users?

How is account recovery and lock out managed for Commonplace users?

Passwords can be reset via email.

Users who have made attempts to login with the wrong password multiple times within a given time period, will be blocked from retrying for a given time. This is a security-based rate limiting policy.

More information: https://commonplace.atlassian.net/l/cp/QiQzDrw8

 Does the system keep an audit trail of user activity?

Does the system keep an audit trail of user activity?

Yes. We keep an audit trail of all key activities, as follows:

  • Admin or comms manager user added / removed

  • Survey user added / removed

  • User log in / log out

  • Create project - retains a record of when a user created a project

  • Change project stage - retains a record of when a user changed the stage of a project

  • Change page stage - retains a record of when a user changed the stage of a page

  • Archived project - retains a record of projects that were archived

  • Renamed project - retains a record of projects that we renamed

  • Content history - we retain history of all saved changes to a page made by any user in the editor

More information: https://commonplace.atlassian.net/l/cp/9hL3pGCT

 Is the application fully accessible?

Is the application fully accessible?

Further detail on how we comply with WCAG 2.1 AA and UK Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 can be found in the Accessibility Policy on the footer of any active Commonplace.

  • No labels