Frequently asked questions.

Inrep Scholar is an institutional repository platform for universities, libraries and research offices. It supports final-year projects, theses, dissertations, journal articles, datasets, public discovery, and compliance reporting, with a review workflow that routes submissions through a supervisor and a librarian before publication.

InRep Connect links to files an institution already hosts elsewhere. InRep Cloud stores files inside Inrep Scholar's own private storage, with a protected viewer and access controls. InRep Campus is installed on the institution's own server — students, staff, submissions and files stay on that server, and only approved published metadata syncs to the central discovery index.

Yes. The platform supports institution-specific repositories, dashboards and public pages, with tenant boundaries enforced on the server for every request — a user from one institution cannot reach another institution's private records by changing a URL, slug, form value or record ID.

Yes. Existing PDFs can be uploaded record by record, or imported in bulk through the bulk upload workflow with row-level validation and duplicate detection.

Yes. The platform is built with PHP and MySQL, so it can be deployed on standard hosting that supports the required PHP extensions and storage permissions — InRep Campus in particular is designed to install on a university's own cPanel or server.

Yes. All of the public research tools are free for anyone browsing Inrep Scholar, with a fair-use rate limit to keep the service available for everyone. No account is required to use them — signing in is only needed to submit or manage your own records.

Tool inputs are used only to generate the requested result and are not published or shared. Published repository records used for search and comparison follow each record's own access policy — a restricted or embargoed record is never surfaced through a public tool result.