Agent Accounts can now use hosted login, which is how an organizer signs in to the Scheduler Editor to create and manage their Scheduler Configurations. Use this when an Agent Account owns a Scheduling Page and someone needs to sign in as that account to edit it. Connected Google and Microsoft grants sign in through an OAuth redirect. An Agent Account signs in with its email address and the app_password set on its grant, the same password it uses for IMAP and SMTP access. Nylas checks those credentials against the existing grant, so it doesn’t create a new grant.
- Agent Account hosted login.
@nylas/login-componentnow shows an email and app-password screen for the Agent Account provider instead of generating an OAuth redirect URL. It lists the provider as “Agent Account”, with a fallback icon when no custom icon is configured. @nylas/identityaddsauthNylas, which submits the email, app password, login ID, and PKCE fields (when present) to verify credentials against an existing Agent Account grant and returns the standard hosted-auth code and tokens.
Before you use it
Section titled “Before you use it”Set an app_password on the Agent Account’s grant first, either when you create the account or later with a PATCH to the grant. See Set an app password for the password requirements. Without one, the Agent Account can’t sign in.