Introduction to public content
Important
This is a closed beta release program.
Beta features should be considered “in development” and may not be fully supported or complete.
Beta programs are invaluable for helping to validate the value and impact of features through feedback and insights. If you would like to participate in beta programs and access this feature, please contact your Customer Success representative.
Overview
Public content is the term used for public pages and public functions, which together make it possible for unauthenticated users (outside of the Skedulo) to access and interact with web content that then feeds back into Skedulo.
Public pages
Public pages enable Skedulo users to publish public-facing content to suit many purposes, for example:
- Documentation; such as catalogs, service guides, and the like.
- Survey response forms to gauge customer satisfaction after work has been done.
- Public booking pages to allow customers to self-manage their appointments.
Public pages can either be static, such as a PDF document or HTML file, or compiled, such as react components.
Public functions
Public functions allow Skedulo functions to be called without a Skedulo authorization header. These are often used in conjunction with public pages. Some public functions may be designed to be fully public (for example, one that accepts bookings from a public appointments page) and some might validate an alternative approval mechanism (for example, a secret token or a social authentication platform) before accepting the function call.
Examples of public functions could include the following items:
- The form response handler for a survey response page.
- An appointment handler for a public booking grid.
- An HTTP endpoint for a triggered action.
- A webhook for a third-party service that can’t pass an authorization header.
Feedback
Was this page helpful?