Authorization
Read as MarkdownMeeting Agents #
Sending a Meeting Agent directly to a meeting needs only
application authentication:
call Schedule/Send a Meeting Agent
with the application’s client_secret and the meeting’s join URL. No calendar
authorization is involved.
When a Meeting Agent should join a calendar event, you
provision it as part of the event
when creating or updating the event.
That call uses the calendar account’s access_token, so it needs one of the
methods in Modular calendar and availability control.
For Zoom meetings Cronofy didn’t create, the meeting owner completes a one-time Zoom authorization.
Conferencing #
Conferencing is added to events through the calendar account’s access_token,
as above. Conferencing services such as Zoom or Webex are then connected in
one of two ways:
- Individually: each user authorizes their own conferencing account. Conferencing Service Authorization generates the link to send them through, so the authorization is linked to their Cronofy account. See With the user’s own conferencing service.
- For an Organizational Unit: an administrator authorizes the company’s conferencing service once, and every member can use it without authorizing individually. See Enterprise Conferencing.