Skip to main content
A saved login holds the sign-in details for one website, such as your Instacart email and password, so a tool can sign in there for you. It is separate from how you sign in to Pomerado; see authentication.

​
How a run uses a login

A tool that signs in uses the site’s saved login. With none saved, the job pauses and asks for one on a protected page; see give a job a login. When a Business account has several logins for the site, pass the one you want as login_id. Pomerado never returns a saved password to a script or a model. Lists show the site, a masked username and the status.

​
Follow your plan’s login policy

On a Personal account, correct a login before its first successful sign-in. After that it is locked, and deleting it doesn’t free the site for another login. On a Business account, each login has its own access list; see share a login.

​
Check a login’s status

  • unverified: no sign-in with it has succeeded yet.
  • verified: a sign-in succeeded.
  • needs_attention: the website rejected it. needs_attention.field names the rejected field.

​
Check permissions

Listing logins needs logins:read. Saving, changing, deleting, importing and revealing them needs logins:manage. See permissions.
  • A login’s ID starts with login_.
  • sign_in is password, or code for a website that sends a code at each sign-in, which saves no password.
  • locked is true for a Personal login after its first verified sign-in.
  • A locked login keeps its username. The one change allowed is a new password, when the website rejects the saved one during a job.