Apps that used user sync still work. You don’t need to set them up again.
What changed
In Zite 1.0, your app’s users lived outside your database. User sync connected those accounts to a table in Airtable or Zite Database and kept the user fields up to date. In Zite 2.0, users are rows in the workspace database alongside the rest of your data. There is nothing to sync, so theSync with database button was removed.
In new apps, you link a table directly to your users instead of copying them. If an app checks an external list before allowing access, use custom access rules.
What happened to your migrated app
During migration, Zite converted your user sync setup into custom access rules on the app:
Your users table remains the source of truth for app access.
Email matching is now case-insensitive. Someone whose row reads
Sam@example.com can sign in as sam@example.com. Zite 1.0 treated those addresses as different.Where to see it
Open your app, go toSettings → Login, then scroll down to Custom access rules. The rules Zite generated for your app are listed there in plain language.
You’ll also see Who can sign up? set to Invite only.
Migrated apps show Invite only because user sync used a closed roster. New apps default to Anyone. The migrated setting prevents people outside the original users table from signing up.
Change how it works now
To change the rules, clickChat about this in the Custom access rules section and describe what you want. For example:
If you’re building a new app
New apps don’t need user sync. Users and app data share the workspace database, so you can link a table directly to them. See Store extra data about your users. Use custom access rules when the list of allowed users lives elsewhere, such as an Airtable base, CRM, or HR system.FAQs
My old apps work fine, but I can't turn user sync on in a new app
My old apps work fine, but I can't turn user sync on in a new app
That’s expected. The button was removed because new apps store users in the workspace database. Most of what user sync did now happens automatically.If your new app genuinely needs to check an external list before letting someone in, ask the Agent to set up a custom access rule. You’ll get the same behavior your migrated apps have.
Do I have to migrate off this?
Do I have to migrate off this?
No. Migrated apps keep working with the rules Zite generated, and there’s no deadline to change them.
Will the generated rules stop working?
Will the generated rules stop working?
No. They’re part of your app now, the same as any other logic in it.
What if I delete the rules?
What if I delete the rules?
Your app falls back to the Who can sign up? setting, and your users table stops controlling access. Anyone the setting allows can sign in, whether or not they’re in your table.If that’s not what you want, leave the rules in place or ask the Agent to adjust them instead of removing them.
Where did my users go?
Where did my users go?
They’re in your workspace database. Open your app’s
Users tab to see everyone who can sign in, or open the workspace’s Members page to see everyone across all its apps.Your old users table is unchanged. It’s still a normal database table, and the app still reads from it.