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

Roadmap question: Compatibility with registered users? #56

Open
Rello opened this issue Apr 21, 2020 · 7 comments
Open

Roadmap question: Compatibility with registered users? #56

Rello opened this issue Apr 21, 2020 · 7 comments

Comments

@Rello
Copy link

Rello commented Apr 21, 2020

Hello,

as the impact of my question is rather complex, I would like to know if you thought about it already for the future:

As Is

  • The app is aimed at external requestors. If an internal user uses it, it could be more integrated

Proposal

  • no need to enter contact data
  • automatic addition into calendar
  • sharing appointment "public page" with user/usergroup

use case:

  • Teacher & Classes

what is your opinion on this feature?

@SergeyMosin
Copy link
Owner

I'll have to look in to this, but this was really made for "external" purposes.

@Rello
Copy link
Author

Rello commented Apr 21, 2020

I am happy to close the issue if you don´t want to have your issue-log spammed...

@SergeyMosin
Copy link
Owner

No, leave it open. Someone might come along and contribute some code if it gains traction.

@SergeyMosin
Copy link
Owner

"Private" mode is available in v1.12.0 more info #298 (comment)

@JocelynDelalande
Copy link
Contributor

@SergeyMosin I was thinking : maybe the easy (and helpfull) part of that feature request would be the following items :

  • if logged-in user and private mode : do not show the name and email fields
  • fill those « fields » from NC logged-in user data

@CSDUMMI
Copy link

CSDUMMI commented Nov 14, 2023

I'd be willing to look into implementing a feature to fill-in the contact info from the current user into the email and telephone field (if present).

I believe this ought to be a pre-filled field that the user can subsequently review and change if they wish.

@JocelynDelalande
Copy link
Contributor

I think « locked » filling also has a use, as it allows registered booking. Anyway, wether the email or phone are « forced », it could be a good idea to store the user ID / user handle on the booked the event, maybe in a ical event property ?

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

No branches or pull requests

4 participants