[GH-ISSUE #1005] Read only user can create project, can we have "true" read only users ? #702

New issue

Open

opened 2026-02-25 23:43:19 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 23:43:19 +03:00

Owner

Originally created by @hugosxm on GitHub (May 24, 2024).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/1005

Hi,

First : Thanks for this amazing software !

Everything is in the title, When I share a project by mail with someone, he can create is own projects and checks even with the fact that registration are disabled. I would like to have to possibility of "true" read only user who can only see the checks and do nothing.

Originally created by @hugosxm on GitHub (May 24, 2024). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/1005 Hi, First : Thanks for this amazing software ! Everything is in the title, When I share a project by mail with someone, he can create is own projects and checks even with the fact that registration are disabled. I would like to have to possibility of "true" read only user who can only see the checks and do nothing.

kerem added the

feature

label

2026-02-25 23:43:19 +03:00

kerem commented

2026-02-25 23:43:19 +03:00

Author

Owner

@cuu508 commented on GitHub (May 27, 2024):

I would like to have to possibility of "true" read only user who can only see the checks and do nothing.

For this, perhaps the read-only dashboard would work?

It comes included in Healthchecks – to access the dashboard for a specific project go to the project's Settings page > API keys > create read-only API key > click on "Read-only dashboard" link.

@cuu508 commented on GitHub (May 27, 2024): > I would like to have to possibility of "true" read only user who can only see the checks and do nothing. For this, perhaps [the read-only dashboard](https://github.com/healthchecks/dashboard/) would work? It comes included in Healthchecks – to access the dashboard for a specific project go to the project's Settings page > API keys > create read-only API key > click on "Read-only dashboard" link.

kerem commented

2026-02-25 23:43:19 +03:00

Author

Owner

@beardedsamwise commented on GitHub (May 29, 2024):

+1 to this. We're using SSO with the OAuth2 Proxy and Okta so this automatically creates users (if they have permission in Okta) and we'd ideally like these to be read only.

@beardedsamwise commented on GitHub (May 29, 2024): +1 to this. We're using SSO with the OAuth2 Proxy and Okta so this automatically creates users (if they have permission in Okta) and we'd ideally like these to be read only.

kerem commented

2026-02-25 23:43:19 +03:00

Author

Owner

@cuu508 commented on GitHub (Jun 10, 2024):

Thinking about this, one unintrusive way to achieve the "auto-created or invited users cannot create their own checks" effect, would be to make the default check limit for new users configurable (as a new instance-wide configuration parameter).

On Healthchecks.io the default limit is currently hardcoded to 20, and on self-hosted instances it is currently hardcoded to 10000.

If the limit was configurable, site operator could set it to 0, and manually increase it up via admin UI for any accounts that do need the ability to create checks. And we could hide the "Add Project" functionality for users with check_limit=0, because it makes little sense to create projects if you will not be able to create any checks in them.

@cuu508 commented on GitHub (Jun 10, 2024): Thinking about this, one unintrusive way to achieve the "auto-created or invited users cannot create their own checks" effect, would be to make the default check limit for new users configurable (as a new instance-wide configuration parameter). On Healthchecks.io the default limit is currently hardcoded to 20, and on self-hosted instances it is currently [hardcoded to 10000](https://github.com/healthchecks/healthchecks/blob/24e5e83bbcdd221e99642c0265251f8cbbf0bf0d/hc/accounts/models.py#L61). If the limit was configurable, site operator could set it to 0, and manually increase it up via admin UI for any accounts that do need the ability to create checks. And we could hide the "Add Project" functionality for users with check_limit=0, because it makes little sense to create projects if you will not be able to create any checks in them.