Chris Hill-Scott 3968d5b766 Allow org team members to see team and usage ...

Organisation team members will be ultimately interested in the detailed
usage of each service, but shouldn't necessarily have access to the
personal data of that services users.

So we should allow these organisation team members to navigate to live
services usage page from the organisation page. They may need to contact
the team so they should also be able to view the team members page.

So they'll then see just usage and team members pages.

If they are actually a team member of the service they're viewing, then
they'll see the full range of options as usual.

This commit implement the above by adding an extra flag to the
`user.has_permissions` decorator which allows certain pages to be marked
as viewable by an organisation user. The default (for all other existing
pages) is that organisation users don’t have permission.

2019-06-20 15:37:52 +01:00

..

__init__.py

Wrap a model around list of all organisations

2019-06-17 16:00:59 +01:00

organisation.py

Wrap a model around list of all organisations

2019-06-17 16:00:59 +01:00

roles_and_permissions.py

Make user API client return JSON, not a model

2019-06-05 11:13:41 +01:00

service.py

Use new fields for getting orgs and services

2019-06-17 15:56:59 +01:00

template_list.py

Make user model return a service model, not JSON

2019-06-13 13:47:28 +01:00

user.py

Allow org team members to see team and usage

2019-06-20 15:37:52 +01:00