Either clarify or remove organization-level roles

[iaindillingham]

As well as project-level roles, Job Server can record organization-level roles. In practice, it doesn't because:

• they aren't exposed in the UI
• they aren't audited¹
• it's unclear how they would interact with project-level roles
• it's unclear whether there is an IG process associated with them

@CLStables suggests either clarifying why organization-level roles exist, and describing the work that would be required to implement them fully, or removing them.

---

@CLStables created this issue as a draft, following a Slack discussion.¹ It contained two actions, which related to organization roles and the Leaver Checklist. This issue relates to organization roles. #4197 relates to the Leaver Checklist.

Footnotes

1. The audit log contains entries for three events: User added [to project], User removed [from project], and User's roles updated [in project]. ↩ ↩²

[lucyb]

We would also need to decide how the involvement of multiple organisations in a project affects org-level roles. I vote strongly for removing them and revisiting the whole approach if it becomes necessary.

Output checking might be an area where org-level roles are useful, but they haven't been needed so far (thread).