App permissions are stored on the user's account. For a crew member or rep with no account, the editor drops that half of the panel and shows a short line saying why — noting that crews reach their work through their field link, so most never need a login — with a button that pre-fills the invite form from their row.
Also called: can't set permissions for my framer · no login · invite to log in
- 1The roster marks each person with hasLogin.
- 2Without a login the permission grid is replaced by the explanation card and the Invite to log in button.
- 3The button copies the person's name, email, phone and role into the Add Member form and opens it.
- 4Role choices also narrow for a login-less person, so Admin is never offered to someone with no account to hold it.
Two comments make the reasoning explicit: 'app permissions for a person with no app account are a control with nothing behind it', and a design note that the screen 'says so and offers the thing that would change it, rather than showing 32 checkboxes that quietly go nowhere'. A related decision — no NO LOGIN chip on every row — records that on a builder's roster most of the crew has no account, so a chip on eighteen of nineteen rows marks nothing out.
- Permission checkboxes were shown for people whose changes had nowhere to persist.
- The path from a roster entry to a real account was not obvious.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →