Authenticated Users Only

%3CLINGO-SUB%20id%3D%22lingo-sub-128293%22%20slang%3D%22en-US%22%3EAuthenticated%20Users%20Only%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-128293%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20started%20to%20have%20a%20look%20at%20bookings%2C%20mainly%20for%20internal%20training%20workshops%20and%20not%20for%20external%20customers.%20I%20am%20wondering%20if%20we%20can%20lock%20down%20access%20to%20the%20published%20calendar%20to%20only%20authenticated%20users%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-128293%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ebookings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-224584%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticated%20Users%20Only%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-224584%22%20slang%3D%22en-US%22%3E%3CP%3Ewe%20have%20a%20similar%20requirement%2C%20is%20to%20make%20bookings%20service%20available%20for%20authenticated%20users%20only%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-179206%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Authenticated%20Users%20Only%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-179206%22%20slang%3D%22en-US%22%3E%3CP%3EI%20would%20also%20like%20to%20know%20if%20there%20is%20a%20way%20to%20block%20users%2C%20we%20don't%20want%20the%20issue%20where%20everyone%20wants%20a%20booking%20for%20e.g.%20%22jobs%22.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOur%20bookings%20tab%20should%20be%20solely%20used%20for%20new%20or%20existing%20clients%20wanting%20a%20service.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-173635%22%20slang%3D%22en-US%22%3ERE%3A%20Authenticated%20Users%20Only%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-173635%22%20slang%3D%22en-US%22%3EIs%20there%20a%20way%20to%20use%20PowerShell%20to%20allow%20booking%20only%20to%20authenticated%20users%20or%20block%20anonymous%20users%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-172122%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticated%20Users%20Only%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172122%22%20slang%3D%22en-US%22%3EAny%20update%20on%20these%3CBR%20%2F%3E-lock%20this%20App%20to%20internal%20authenticated%20users%20only%20and%20populate%20requestor's%20profile%20automatically%20when%20scheduling%20bookings%3CBR%20%2F%3E-%20make%20published%20URL%20to%20encoded%20URL%20type%20instead%20of%20taking%20Booking%20name%20and%20email%20address%3CBR%20%2F%3E-%20have%20many%20owners%2Fadmins%20to%20the%20booking%20App%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-142344%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticated%20Users%20Only%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-142344%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20expand%20the%20use%20case%2C%20it%20should%20not%20be%20limited%20to%20O365%20users%20on%20our%20tenant%20if%20we%20enable%20authenticated%20users.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20have%20a%20use%20case%20where%20we%20would%20like%20to%20provide%20Bookings%20to%20external%20customers%2C%20but%20we%20don't%20want%20random%20users%20to%20create%20bookings.%20As%20such%2C%20could%20we%20have%20a%20method%20to%20create%20customers%20in%20Bookings%20itself%2C%20a%20bit%20like%20Yammer%20allows%20you%20to%20invite%20external%20users%20to%20your%20Yammer%20network.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-138109%22%20slang%3D%22en-US%22%3ERE%3A%20Authenticated%20Users%20Only%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-138109%22%20slang%3D%22en-US%22%3EAny%20update%20on%20this%20to%20lock%20this%20App%20to%20internal%20authenticated%20users%20only%20%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-130915%22%20slang%3D%22en-US%22%3ERe%3A%20Authenticated%20Users%20Only%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130915%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20also%20looking%20at%20the%20same%20use%20case%20and%20wanted%20to%20know%20if%20access%20could%20be%20locked%20down%20for%20internal%20use%20only.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Deleted
Not applicable

Just started to have a look at bookings, mainly for internal training workshops and not for external customers. I am wondering if we can lock down access to the published calendar to only authenticated users? 

7 Replies

I'm also looking at the same use case and wanted to know if access could be locked down for internal use only.

Any update on this to lock this App to internal authenticated users only ?

To expand the use case, it should not be limited to O365 users on our tenant if we enable authenticated users.

 

We have a use case where we would like to provide Bookings to external customers, but we don't want random users to create bookings. As such, could we have a method to create customers in Bookings itself, a bit like Yammer allows you to invite external users to your Yammer network.

Any update on these
-lock this App to internal authenticated users only and populate requestor's profile automatically when scheduling bookings
- make published URL to encoded URL type instead of taking Booking name and email address
- have many owners/admins to the booking App
Is there a way to use PowerShell to allow booking only to authenticated users or block anonymous users?

I would also like to know if there is a way to block users, we don't want the issue where everyone wants a booking for e.g. "jobs". 

Our bookings tab should be solely used for new or existing clients wanting a service.

we have a similar requirement, is to make bookings service available for authenticated users only