Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restrict custom pages to speakers only #5261

Closed
kiden opened this issue Feb 22, 2022 · 2 comments · Fixed by #5268
Closed

Restrict custom pages to speakers only #5261

kiden opened this issue Feb 22, 2022 · 2 comments · Fixed by #5268
Assignees
Milestone

Comments

@kiden
Copy link

kiden commented Feb 22, 2022

We need to provide information like zoom login details, speaker protocols, etc. to our speakers. This information evolves over the course of an event, so we want to provide it on a web page - which we can continuously update - rather than in a series of emails.
We don't want anyone else to access this information; only the speakers.

What we'd like is to be able to put this information on custom pages and restrict access to 'speakers only'.
For the menu there are two options

  1. show the menu link to all users, but when a non-authorised user clicks the link then display a page with message saying something like "the content of this page is for speakers only (and maybe a suggestion to login if not already logged in). if you are a speaker and think you should have access please contact "
  2. show the menu link only to logged in users who are also confirmed speakers
    (this might cause some users to get in touch asking "where has the menu gone?" if they forget to log in first)
    I think there are usability pros and cons to both options (and maybe some others options I haven't considered)

We have tried series of emails but speakers end up confused if they accidentally don't check the latest one.
We have tried using custom pages, hiding them in the menu, and sending the link by email to speakers. Problem is they keep losing the link and have to ask for a reminder, often in the middle of an event when everyone's busy/stressed. Plus it's not secure - non-speakers could potentially get hold of the link and read and use the content.
What we're doing at the moment is publishing this content on our Confluence wiki instead and restricting it to the event speakers, which involves manually creating a corresponding group of speakers on Confluence and manually keeping it synchronised with the list of speakers on Indico. This also suffers from the problem described above: we have to email them the link and they can't easily find it again when they need it. Plus it means we're storing content across multiple system when it feels like it should be kept together.

@duartegalvao duartegalvao self-assigned this Feb 25, 2022
@ThiefMaster ThiefMaster added this to the v3.2 milestone Mar 4, 2022
@ThiefMaster
Copy link
Member

ThiefMaster commented Mar 4, 2022

This will be included in v3.2 :) The menu entry and page will only be visible to those who can access it.

@kiden
Copy link
Author

kiden commented May 21, 2022

Just doing a bit of housekeeping and realised I never said thank you...

Thank you! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants