Allow secret URL even when public pages are not allowed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
I suggest to separate the allowing of public pages from the use of secret URLs. In an organization that uses Mahara for assessment, you may wish to prevent users from sharing their portfolios with the public to avoid letting sensitive information be searchable in Google, but you may still want to allow them to share their portfolio with an assessor / expert who doesn't have an account on the site or use it to create an employment portfolio to share with a prospective employer who doesn't have access to the system.
Therefore, it would be good if secret URLs still worked even if the site / the institution doesn't allow public pages.
If we should keep the option that a site needs to be locked down for users with accounts only, then a second option should be created to not allow secret URLs on top of not allowing public pages.
Hello Kristina
We have the same concern here
I do vote for this bug (don't know how to vote in the launchpad)
We had to alow public pages so that users can generate secret URL.. But we'd like to prevent users from sharing their portfolio with the public.