Roles and workspace access
The Administration role catalogue provides a starting point for separating portal responsibilities. The role descriptions and default workspaces are proposed design values, not an approved CEDA permission matrix.
Open Administration in the CEDA preview.
1. Review the role templates
The workspace displays eight proposed role templates.
| Role template | Intended responsibility | Default workspace |
|---|---|---|
| Platform administrator | Manages portal accounts, role templates and platform access settings | Administration |
| Funding programme administrator | Configures funding programmes and manages operational funding intake | CEDA Operations |
| Eligibility reviewer | Reviews assigned eligibility cases and records reasoned outcomes | CEDA Operations |
| Evaluator | Completes independent assessments for specifically assigned applications | Evaluator |
| Evaluation panel chair / adjudicator | Reviews authorised evaluation packs and records panel outcomes | Adjudication |
| Innovation rules manager | Maintains intake, eligibility, evidence, assessment rubric and funding workflow rules | Innovation Rules |
| Applicant / organisation lead | Manages an organisation profile, team access and its own submissions | Applicant |
| Applicant team member | Contributes to applications shared by the organisation lead | Applicant |
2. Review the role cards
- Scroll to Role templates & permissions.
- Read the role name and responsibility description.
- Read the scope note under each description.
- Check the default workspace pill at the bottom of the card.
- Compare the scope with CEDA's proposed segregation-of-duties requirements.
The scope notes are intentionally narrow. For example, an evaluator is described as working on assigned submissions and their own assessment, while an adjudicator is intended to see authorised panel cases and preserve evaluator submissions as read-only.
A platform administrator defaults to Administration; the template does not automatically grant access to applicant idea content.
3. Read the default role-to-workspace matrix
The Default role-to-workspace matrix displays all eight roles against six workspaces.
| Role | Administration | CEDA Operations | Applicant | Evaluator | Adjudication | Innovation Rules |
|---|---|---|---|---|---|---|
| Platform administrator | ● | ○ | ○ | ○ | ○ | ○ |
| Funding programme administrator | ○ | ● | ○ | ○ | ○ | ○ |
| Eligibility reviewer | ○ | ● | ○ | ○ | ○ | ○ |
| Evaluator | ○ | ○ | ○ | ● | ○ | ○ |
| Evaluation panel chair / adjudicator | ○ | ○ | ○ | ○ | ● | ○ |
| Innovation rules manager | ○ | ○ | ○ | ○ | ○ | ● |
| Applicant / organisation lead | ○ | ○ | ● | ○ | ○ | ○ |
| Applicant team member | ○ | ○ | ● | ○ | ○ | ○ |
The initial matrix assigns one default workspace per role. It is a starting configuration for review, not a complete access-control specification.
4. Understand additional workspace assignments
The Add preview account form and the directory's access editor allow the administrator to select more than the default workspace.
- Start with the role's default workspace.
- Add another workspace only when the test case requires it.
- Record the reason for a broader scope outside the prototype if the design review requires an approval trail.
- Recheck the workspace list whenever the role template changes, because selecting a new role resets the workspace selections to the new role's defaults.
The role-to-workspace matrix shows the default. It does not change to display each user's custom workspace values.
5. Understand delegated onboarding
The account form and access editor include May onboard other people. In the current open preview, the only selectable scope is Their applicant team members only.
This is intended for an applicant lead who may prepare invitations for people contributing to that organisation's applications. It is not authority to invite CEDA staff, evaluators, adjudicators or privileged administrators.
The open preview stores the flag as a descriptive profile value only. It does not grant a working delegated invitation capability.
6. Keep process roles separate from portal roles
Innovation Rules and Administration solve different problems.
| Workspace | Question it answers |
|---|---|
| Innovation Rules | Which function owns each funding-process stage, and what information scope is intended for that function? |
| Administration | Which portal role template and default workspace should be associated with a user? |
For example, Independent evaluator in Innovation Rules describes a process function. Evaluator in Administration is a proposed portal role template. They may be related, but neither definition alone authenticates a person or enforces access.
7. Controls still required before production
The matrix does not specify the full record-level permissions, approval limits, authority to make or release funding decisions, data ownership, document permissions, delegated authority or every conflict-of-interest restriction.
CEDA must approve the role catalogue, approvers, separation of duties, record and file scope, workspace access, delegation rules and sensitive action permissions before these values can be enforced in production. Server-side APIs must independently verify a user's session, role, assignment and record relationship.