Open Journal Systems role separation is the review boundary, not the login page

Open Journal Systems manages editorial workflows for scholarly publishing. A single installation can host several journals, and a user can hold different roles in each one. The role model is central to confidentiality because reviewers, authors, editors, and journal managers need different views of submissions, discussions, files, and publication decisions.

A count-only ZoomEye query for title="Open Journal Systems" returned 1,227 matches on 2026-11-10 at 00:51 UTC. The alternate title="OJS" returned 693, the application query returned zero, and http.body="Open Journal Systems" returned 21,336. The body count is a broad textual marker. The title counts are a more practical discovery baseline but still do not prove the page is an active journal.

View the Open Journal Systems title measurement in ZoomEye. The query used page 1, page size 1, and sub_type=all.

One installation, many role boundaries

The OJS user guide describes roles that map to workflow stages and responsibilities. A user can be an Editor in one journal and only an Author in another. The Journal Manager manages journal setup and user accounts. The documentation also warns that journal managers should be treated as highly trusted because they can assume the identities of other users enrolled in other journals.

That is the key review point. An installation hosting multiple journals may have a strong editor in one journal who should not see another journal's submissions. A manager role, an account recovery path, or a session feature that crosses journal boundaries can weaken that separation.

Inventory each journal, its manager accounts, editor roles, reviewer access, and site-level administrators. Review who can enroll users, change roles, and impersonate another account. Test with two journals and an account that has a narrow role in only one. Confirm that direct URLs and API calls enforce the journal context.

Submission files and review confidentiality

OJS stores manuscripts, supplementary files, review comments, decision letters, and correspondence. Some files may be public after publication, while others must remain confidential during review. A role that can list a submission is not necessarily allowed to download every file or see every discussion.

Test the download and discussion paths with the narrow account. Check whether an expired reviewer assignment still leaves review files accessible. Check what happens when a user is removed from a role but remains enrolled in the journal. Removal from one role is not the same as deleting the account.

The OJS guide notes that removing a user from a role does not necessarily delete the account. That lifecycle distinction belongs in the access review. Former editors and reviewers may retain an account that can authenticate even if their active roles have changed.

Discovery and validation

Use the title counts to find candidates, then confirm a small sample in an authorized way. The alternate OJS title is a useful second query, but the acronym can appear in unrelated pages. The body query is even broader. A zero app fingerprint means the tested value did not match, not that OJS deployments are absent.

Record the installation URL, visible version, journal count, authentication method, account registration policy, and owner. Compare external candidates with the internal list of journal platforms. A hosted service may be owned by a publisher, library, or research group rather than central IT.

The useful conclusion

ZoomEye shows that product-title markers identify a population large enough to warrant an inventory. It does not show that 1,227 journals are exposed or that their review files are public. The security decision comes from role testing and file authorization.

The goal is a platform where every journal has an owner, every role has a purpose, and a user cannot cross a journal boundary through an old role, a manager function, or a direct object URL. The login page is the visible edge. The editorial workflow is the data boundary behind it.

References

• OJS user account overview
• OJS roles
• OJS users and roles management
• ZoomEye title measurement for Open Journal Systems

Measurement metadata: 2026-11-10 00:51 UTC, sub_type=all, page 1, pagesize 1; title 1,227, alternate title 693, app 0, body 21,336.