Delib | Developer Docs
Knowledge Base
  • Delib
    • 👋Welcome
    • Our Products
  • Security Centre
    • Information Security
      • Service Level Agreement (SLA)
      • Disaster Recovery
      • Certifications
      • Information Security Downloadable Documents
    • Privacy and GDPR
      • How do Delib's products comply with the GDPR?
      • Delib Sub Processors
  • Citizen Space
    • Getting Started With Citizen Space
    • Deployment Requirements
      • How to set up a CNAME record for a custom domain name
      • Department structures
      • Users and permissions
      • Theming requirements
    • Security Configurations
      • Single Sign On (SSO)
        • Citizen Space Single Sign-on (SSO) - Linking Accounts
      • Two factor authentication (2FA)
      • Configurable password policy
      • Log in back-off
      • Security Notifications
      • Password reset date on export
      • Session Length
    • Integrations
      • How to integrate Citizen Space into existing website
    • Data API
      • API specification
      • Generating API keys
      • Basic Auth headers with Citizen Space
    • Public API
      • Public API v2.x guide
      • Version 2.4 reference
    • Webhooks
      • Creating and managing webhooks
  • Geospatial
    • Set-up process for existing customers
      • How to find your Ordnance Survey API key
      • Linking your Ordnance Survey account to Citizen Space
  • Integrations and Playbooks
    • Google Looker Studio
      • Google Looker Studio
      • Google Looker Studio Simple Activity Counts
    • Microsoft
      • PowerBI Dashboards
Powered by GitBook
On this page
  • Stage one - Deploying your Citizen Space site
  • A couple of extra things to note:
  1. Citizen Space

Deployment Requirements

PreviousGetting Started With Citizen SpaceNextHow to set up a CNAME record for a custom domain name

Last updated 1 year ago

Preparing your Citizen Space site to go live to the public is a two-stage process:

  1. : the term we use for the technical aspects of setting up your Citizen Space site; and

  2. : the things you need to do after deployment to get your Citizen Space site ready to go live to the public.

Stage one - Deploying your Citizen Space site

There are a number of things we need from you in order to deploy a Citizen Space site. Once you have gathered these, please email them to your customer success manager:

1) Citizen Space URL

As each Citizen Space site has its own web address (URL), you will need to have a URL set up for this purpose. There are two options for the URL that your Citizen Space site can have:

  • It can have a similar web address to your main site, or a project name, for example: 'haveyoursay.clientname.gov.zz' or 'clientnameprojectname.com'. If you would like this type of URL, you'll need to ask your technical team to register the subdomain and create a CNAME record (this is the technical name for something on our web server that points to another location). We will provide the CNAME address for your technical team to use for this. Please see .

  • If you prefer to use our Citizen Space domain (eg. 'clientname.citizenspace.com'), you will need to let us know what you would like the ‘clientname’ part of the address to be.

2) A contact email address

You will need to supply us with an email address to use for correspondence that comes from your Citizen Space site. We will then set up a 'yourorganisation@mail1.citizenspace.com' email address (you can choose the words that appear before the @). The latter will be the address that all of your general Citizen Space emails come FROM and any contact form messages go TO. This email will be routed to the generic email address you provided.

For more information, please see the article

3) Site admin details

When we deploy the site we will set up your first user and give them "Site Admin" permission, i.e. the highest level of access across the site. This person will then be in a position to register anyone else from the organisation who needs to be able to access Citizen Space. We therefore need their full name, email address, work contact phone number and job title.

4) Department name

Please choose the name for the first department on your site. This is the department your site admin user will belong to. Citizen Space uses a department-based structure to enable you to manage users' access to the data they need.

This can be important as the name of this department will also appear in the URL of every activity that belongs to this department ie: https://example.citizenspace.com/department-name/activity-title

5) A corporate logo

You will need to supply us with a high quality logo to go at the top of your Citizen Space site. Ideally, logo dimensions should be no taller than 100px and preferably no wider than 250px.

6) Brand colours

The colour of your Citizen Space buttons, heading text, and title blocks can be customised to your desired corporate colour(s). Ideally, if you can send your brand guideline colours to us this will allow us to choose the most appropriate ones for your site. If this isn't possible, please provide your colour choices as hex values, such as '#CC9966'. If you do not know the hex value of your colour, please supply us with the website address where we can find the colour(s) you want to use. Please note that we must take into account colour contrast ratios from web accessibility guidelines when setting the colour of text and other items.

7) A favicon (optional)

A favicon is a tiny image which sits in the browser bar and tab heading when someone is on your site. If you can send us your preferred favicon image, we will apply this to your site. If this isn't possible, then we may be able to take the image from other sites you own.

8) The site-wide background wallpaper (optional)

You can have a full-width wallpaper image on your site, which really makes your site come alive.

To find a good image think in terms of wallpapers which usually have repeating elements and still look good if the sides, top or bottom are cut off. Avoid images with text, logos or specific focal points. This is because the image is used as a background image and what you can see of the site-wide wallpaper will be different on different sized devices. There is no guarantee a user will see any specific part of this image as it sits behind other items on the page.

Please supply an image that is around 3000px wide by 1000px tall. This allows us to crop and resize the image as required. Please note that this is not a set image size as how tall the image depends on how much text you have on your site homepage. Our recommendation is to keep the hub text succinct and use the 'About' page for further detail about how your organisation approaches consultation and engagement.

9) If your subscription includes Geospatial (this is optional and not included in all Citizen Space subscriptions as standard)

If deploying Geospatial for Citizen Space you will also need your organisation’s Ordnance Survey API Key (if applicable). You (or a relevant colleague from your organisation) will add these directly into your Citizen Space so you do not need to send them to us, but you will need them for stage two when you are preparing your site to go live to the public.

A couple of extra things to note:

SSL certificate

Citizen Space Aggregator site

You don't need to provide an SSL certificate, we will organise and purchase one on your behalf. We will need to know your Citizen Space site's URL (see item 1 above) prior to this taking place. You can .

We provide an which gathers together all of the public activities happening across Citizen Space sites around the world and puts them all in one place for other organisations to browse. This site is publicly accessible but will only ever show activities that are already in the public domain. Please let your customer success manager know before your site is deployed if there's any reason why you would prefer for it not to appear on the Aggregator.

Deployment
Preparation
our article explaining setting up a DNS CNAME record
What is the site email address used for?
learn more about SSL certificates
Aggregator site