dropbits Documentation

Log in & roles

Self-hosted sites use a normal login page. After you authenticate, Dropbits shows the hub and per-section Content / Layout handles when your grants allow edit.

Log in

  1. Open /login on your site, or the footer Log in chip when the site has one.
  2. Enter username and password.
  3. You return to the page you came from (or home).

Forgot password: on the login form → email reset link → set a new password. This only works when mail is enabled and deliverable (not log-only on a live site). See Packs & capabilities.

Invite an editor

Admins add people under Hub → Records → Users (staff listing; Admin-only):

  1. Open Users.
  2. + Create record (or the listing’s create control).
  3. Set email and either a password, or email only and have them use Forgot password.
  4. Give them the editor role (or whatever grant set your site uses for content work).

What the new person sees: Records, Account, Help, and Content / Layout on pages they can edit — not Pages, Site, or Backup unless you grant those.

On a live site, reset and invite mail must actually reach the inbox. Set From under Site after enabling mail.

Account (Hub → Account) is your own user row — change your password there when the listing allows it.

Default admin (demos)

Non-live demos often seed user admin with password admin unless an operator set a real password. Live sites refuse that default. Change any seeded password after first login on a shared demo.

Roles

RoleTypical use
GuestAnonymous visitors — public pages only
EditorContent edits + hub Records / Account / Help (no Pages / Site / Users unless granted)
AdminFull structure: Pages, Entities, Site, Backup, packs, Users

What you see in the hub is grant-filtered. Missing items usually mean your role lacks that capability — not a broken UI.

Page visibility

Who can view a page is separate from who can edit. Hub → Pages sets Public / Editors / Admin / Nobody per row — see Pages & navigation.

See also