Researcher profile publishing
Lecturers maintain profile details internally. Reviewers check quality, compliance, visibility, and repository records before admins publish public pages.
Public profiles
1
Published lecturer and researcher pages.
In review
1
Profiles waiting for reviewer or admin action.
Repository records
10
Outputs, datasets, software, media, and reports.
Internal profile register
Profile records connect user roles, repository visibility, project outputs, and public publishing status.
Dr Amina Patel
Associate Professor in Digital Public Health
Population Health Sciences - amina.patel@northbridge.ac.uk
Owen Griffiths
Senior Research Development Manager
Population Health Sciences - owen.griffiths@northbridge.ac.uk
Publication workflow
Public profile visibility policy
Recommended defaults for what staff can publish publicly, what reviewers should check, and what must stay internal.
Public by default
5
Controlled internally
4
Need review
5
| Profile field | Category | Default | Owner | Reason |
|---|---|---|---|---|
Public name, title, position, department Reviewer approval required before public release. | Identity | Public | Academic | Core public profile identity and affiliation details should be visible once checked by the profile reviewer. |
Biography, expertise keywords, research interests Reviewer approval required before public release. | Research | Public | Academic | These help external visitors, collaborators, and students discover relevant expertise without exposing sensitive project data. |
ORCID, Google Scholar, institutional repository links Reviewer approval required before public release. | Repository | Public | Academic | Public identifiers improve discoverability, but links should be checked before publishing. |
Published publications, datasets, software, reports, media Reviewer approval required before public release. | Repository | Public | Research Manager | Only outputs marked Public and Published should leave the internal repository workflow. |
Supervision areas and public contact preference Reviewer approval required before public release. | Teaching | Public | Academic | Useful for prospective students, but should remain optional for staff who do not supervise or accept public contact. |
Draft edits, reviewer comments, profile checklist Governed by internal role permissions. | Governance | Reviewer Only | Admin | Review evidence is operational governance data and should be visible only to assigned reviewers and administrators. |
Sensitive projects, ethics flags, contracts, due diligence Governed by internal role permissions. | Governance | Internal | Admin | These records may contain confidential partners, legal terms, personal data, or ethics risks. |
Budgets, costings, salaries, partner costs, overheads Governed by internal role permissions. | Governance | Internal | Finance Officer | Financial details should stay internal unless a funder or public reporting process explicitly approves a summary. |
Uploaded files, draft proposals, support letters, internal emails Governed by internal role permissions. | Governance | Private | Admin | Files should inherit project permissions and never appear on public pages by default. |
Recommended improvements
High-value next steps for making profile publishing safer and more useful for universities.
Side-by-side public preview before publish
Profiles
Reviewers can compare internal fields against the exact public page before approval.
Field-level locks after reviewer approval
Governance
Approved public fields cannot be changed without re-entering review.
CMS publish and unpublish webhooks
Integrations
University websites can update staff pages automatically when a profile is published or withdrawn.
AI sensitive-data redaction check
AI
AI can warn reviewers if public text mentions confidential partners, budgets, ethics issues, or unpublished outputs.
Public profile engagement analytics
Analytics
Departments can see profile completeness, publication freshness, and external engagement trends.