mahara-contributors team mailing list archive

[Kristina Hoeppner <1394830@xxxxxxxxxxxxxxxxxx>]

The user option for noindex sounds the best as the site admin or
institution admin can't foresee what a user wants. Though thinking of
smaller children, they may not completely understand what the option is
for and thus, a noindex option could be forced.

This brings up the question also that we should consider public pages
for certain roles, e.g. don't allow public pages for regular users, but
for staff and admin. I filed wishlist item bug#1429325 for that.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1394830

Title:
  Allow secret URL even when public pages are not allowed

Status in Mahara ePortfolio:
  Triaged

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1394830/+subscriptions