Sign-up form and attributes

Sign-up can collect more than an email and a password. Attributes are the details you ask for, such as name, company or date of birth. You decide which are asked and which are required, and Pawabase enforces it on the sign-up API as well as on any hosted page, so a custom form cannot skip it.

Attributes page — Users & auth → Attributes: each detail is Off, Optional or Required, with an Admin-only edits box.

In Studio

Two pages work together:

Sign-in & registration → Sign in with and Registration (identifiers and form layout).
Attributes (the details themselves).

Which identifiers a person can type on the sign-in page. Email is always collected, because verification and recovery go there. You can also allow Username and Phone number. A username or phone number you allow for sign-in becomes required at sign-up and must be unique.

Standard attributes

For each detail, choose whether sign-up asks for it. Each can be Off, Optional or Required: First name, Last name, Full name, Username, Phone number, Date of birth, Gender, Company, Job title, Website, Country, Address. Email and password are always asked.

Custom attributes

Add your own with Add attribute:

Field	Meaning
Label	What the person sees
Key	The name you read in code (`plan`, `team_size`)
Type	Short text, Long text, Number, Date, Phone, Web address, Choice, or Checkbox
Choices	For Choice: the allowed values, separated by commas
Minimum / Maximum	For text and long text, the fewest and most characters; for numbers, the smallest and largest value
Help text	A short hint shown under the input

Two switches on each attribute:

Only an administrator can change it once it has a value. Use for things people shouldn’t edit after sign-up, like a plan.
Include this attribute in the access token. Copies it into the token so access rules and your API can read it without a lookup.

Access token contents

Under Access token contents, Attributes in the token lists which profile attributes are copied into the access token. The mode is all by default.

In your app

Send the values with data when you sign up. They land in user_metadata:

await pawabase.auth.signUp({
  email, password,
  name: "Ada Lovelace",
  username: "ada",
  data: { company: "Analytical Engines", team_size: "6-20" },
});

pb.auth.sign_up(
    email=email, password=password, name="Ada Lovelace", username="ada",
    data={"company": "Analytical Engines", "team_size": "6-20"},
)

If a required attribute is missing or invalid, sign-up fails with a ValidationError naming the field, so you can show it under the input:

catch (e) {
  if (e instanceof ValidationError) setErrors(e.byField());   // { team_size: ["is required"] }
}

Read them back from user.user_metadata. Attributes marked admin-only can’t be changed by the person afterwards with updateUser.

Designing the form

Ask for the minimum. Every extra required field loses people.
Use Choice instead of free text where you’ll filter or segment later.
Put long forms across two steps.
Mark anything that drives permissions or billing as admin-only, and put the value you need in the token.

The user profile

Edit attributes later.

Sign-up restrictions

Control who can join.

Getting started

Sign-in methods

Sign-up

Security

People

Developers

Sign-up form and attributes

In Studio

Standard attributes

Custom attributes

Access token contents

In your app

Designing the form

The user profile

Sign-up restrictions

​In Studio

​Sign in with

​Standard attributes

​Custom attributes

​Access token contents

​In your app

​Designing the form

The user profile

Sign-up restrictions

In Studio

Sign in with

Standard attributes

Custom attributes

Access token contents

In your app

Designing the form