Chris Hill-Scott d7e03e00d3 Storing more info about an organisation ...

Currently we have
- a thing in the database called an ‘organisation’ which we don’t use
- the idea of an organisation which we derive from the user’s email
  address and is used to set the default branding for their service and
  determine whether they’ve signed the MOU

We should make these two things into one thing, by storing everything
we know about an organisation against that organisation in the database.
This will be much less laborious than storing it in a YAML file that
needs a deploy every time it’s updated.

An organisation can now have:
- domains which we can use to automatically associate services with it
  (eg anyone whose email address ends in `dwp.gsi.gov.uk` gets services
  they create associated to the DWP organisation)
- default letter branding for any new services
- default email branding for any new services

2019-03-08 13:30:32 +00:00

..

test_invite_rest.py

- new endpoint to check the token for an org invitation.

2018-02-23 10:45:18 +00:00

test_rest.py

Storing more info about an organisation

2019-03-08 13:30:32 +00:00