[FEATURE REQUEST] Multiple quality-of-life feature requests #1418

New Issue

MrUnknownDE · 2026-04-05T19:26:42+02:00

MrUnknownDE commented

2026-04-05 19:26:42 +02:00

Originally created by @kmanwar89 on 6/2/2025

Hi,

I'd like to request if the following features can be evaluated for their feasibility for implementation into Pangolin. I feel these features would add significant value and improve the product by adopting a security-first mindset.

Ability to define rule "templates" to apply to multiple resources - I currently have 50+ resources in Pangolin, and it's a good bit of work to add the same rules to each resource (allow my WAN IP range, allow Tailscale IP range, allow my VPS IP, block all others). I'd like to see if the ability to "apply rule to selected" could be implemented as this would save time immensely. Alternatively, a "rules template" that could be selected and applied to a resource as it was created would accomplish the same effect.
Edit user details after creation - currently, a Pangolin admin is not presented the option to edit optional details about a user (First/Last name, email) once the user is created. As an admin, I should be able to edit a user's details, generate a password reset or one-time login code, etc. to help a user who gets locked out regain access to their resources.
Implement a configurable session timeout - this is a security issue, and means that if a bad actor gets access to Pangolin, it will never timeout. A configurable session timeout is a standard security feature and should be implemented to prevent unlimited access to the admin interface in case of a credentials breach/exposure.
List, or allow a user to select, resources assigned to them. Currently, if a user logs into Pangolin as a non-admin account, they are presented with a count of sites, users, and resources, but cannot "do" anything with this information. I think there would be value in allowing a user to see which resources they can access. If the "sites" count for a user always lists 0, then perhaps there is value in removing that from the UI as it's not something a user can interact with or provides them anything worthwhile.

Again, thank you for this awesome project. I wish I were more of a developer and could contribute PR's, but alas, I can just try to raise the issues and hope the rationale/justification is valid. Thanks again!

*Originally created by @kmanwar89 on 6/2/2025* Hi, I'd like to request if the following features can be evaluated for their feasibility for implementation into Pangolin. I feel these features would add significant value and improve the product by adopting a security-first mindset. 1. Ability to define rule "templates" to apply to multiple resources - I currently have 50+ resources in Pangolin, and it's a good bit of work to add the same rules to each resource (allow my WAN IP range, allow Tailscale IP range, allow my VPS IP, block all others). I'd like to see if the ability to "apply rule to selected" could be implemented as this would save time immensely. Alternatively, a "rules template" that could be selected and applied to a resource as it was created would accomplish the same effect. 2. Edit user details after creation - currently, a Pangolin admin is not presented the option to edit optional details about a user (First/Last name, email) once the user is created. As an admin, I should be able to edit a user's details, generate a password reset or one-time login code, etc. to help a user who gets locked out regain access to their resources. 3. Implement a configurable session timeout - this is a security issue, and means that if a bad actor gets access to Pangolin, it will never timeout. A configurable session timeout is a standard security feature and should be implemented to prevent unlimited access to the admin interface in case of a credentials breach/exposure. 4. List, or allow a user to select, resources assigned to them. Currently, if a user logs into Pangolin as a non-admin account, they are presented with a count of sites, users, and resources, but cannot "do" anything with this information. I think there would be value in allowing a user to see which resources they can access. If the "sites" count for a user always lists 0, then perhaps there is value in removing that from the UI as it's not something a user can interact with or provides them anything worthwhile. <img width="632" alt="Image" src="https://github.com/user-attachments/assets/d6597ac1-0d18-4c8b-94e1-efc3450a794e" /> Again, thank you for this awesome project. I wish I were more of a developer and could contribute PR's, but alas, I can just try to raise the issues and hope the rationale/justification is valid. Thanks again!

MrUnknownDE closed this issue

2026-04-05 19:26:42 +02:00

Sign in to join this conversation.

Branches Tags

main

dev

dependabot/npm_and_yarn/dev-minor-updates-b4e5d6b9c5

revert-2766-feature/systemd-install-instructions

dependabot/npm_and_yarn/prod-patch-updates-05702d39f2

dependabot/npm_and_yarn/next-16.2.1

dependabot/npm_and_yarn/recharts-3.8.1

alerting-rules

private-site-ha

dependabot/docker/docker/library/node-25-slim

ssh

delete-account

msg-delivery

org-only-idp

cicd

patch

site-targets-auto-login

No Label enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement help wanted help wanted help wanted help wanted help wanted help wanted help wanted help wanted help wanted help wanted help wanted help wanted help wanted help wanted help wanted help wanted

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pangolin#1418