🔒Pyas Auth vs Native Auth

What are the authentication options?

Pyas Authentication

When you sign up for Pyas and create an app, Pyas Authentication is enabled by default. This helps you get up and running quickly and allows you to start connecting Google, Outlook, and Zoom accounts in a matter of minutes. The consent screens that your user will see when you try to connect to their accounts, using the Pyas Authentication option, will display the Pyas name and logo. Overall, this is the quickset option to get you started and add calendar integrations into your app.

Native Authentication

The Native Authentication option is recommended when you want to completely customize the authentication experience for your users. Your users will authenticate directly in your app without redirecting them to Pyas. They will never know that you're using Pyas behind the scenes to handle your calendar integration needs. You will have full control over the process, look and feel of the login/consent experience.

Keep in mind that using the native authentication option requires you to set up provider apps with the third-party providers you use (Google, Microsoft or Zoom). This is more complicated than using the Pyas Authentication option and takes a bit longer to get setup. Also, keep in mind that you will have to get your provider apps verified by Google, Microsoft, or Zoom (whichever providers you use). If you don't require any customization and don't mind your users seeing the Pyas name and logo on the consent screens, use the simpler Pyas Authentication option.