Skip to main content
A member opens their sites from the account menu, and /accounts takes them to one of them. This page covers what the menu lists, where /accounts opens, and the choices a member and a company can make: pins, a home site, removals and featured sites. None of these choices gives anyone access to a site. They only arrange what the menu shows. The CLI has no command for any of this. Use the member API for a member’s choices and the company API for the company’s.

​
Read the account menu

Fluid draws the account menu outside the site’s frame, on every page. Read the same menu with Show the member’s account menu. It lists the sites a member can open in four groups:
  • A site no share reaches is in no group. A public site opens at its address, but it appears in a member’s menu only when a share reaches that member. To list a company site for every member, share it with a segment that names no member type and no country. See Share a site.
  • A member’s shared sites are capped at 100. The menu lists the newest 100 and says how many it left out. A site the member pinned, a site the company features and the member’s home site are listed even when they fall outside the newest 100.
  • The menu is read when you ask. A removal or a restored site shows in the next read.
  • It takes a member’s own credential, sent as a bearer token. A request on the cookie mount is refused, and so is the credential order and subscription emails carry. See Build with the APIs.

​
Know where members land

A member who opens /accounts is sent to one site. A guest is sent to sign in first. Fluid goes down this list and sends the member to the first site it can open at its home page:
  1. The member’s home site, when they chose one.
  2. The first company site the member hasn’t removed.
  3. The first company site, when the member removed every one.
  4. The member’s own sites, newest first.
Fluid skips a site the member can’t open, and a site with no served home page. If none is left, /accounts shows a page that says the member has no site yet. So a site with no published home page never catches a member. See Pages and menus. The menu names the first of these as landing_site_id, before Fluid checks that it can open the site.

​
Choose a home site

A member can choose one site as their home. /accounts opens it first.
  • Choose it with Choose the member’s home site. Clear it with Clear the member’s home site, and /accounts opens where it would without a home.
  • The site must be published. It can be the member’s own, a company site or a site shared with them. It doesn’t have to be pinned. A site the member removed from their menu, or a draft, is refused. A site the member can’t see is not found.
  • A home that can’t be opened is ignored. If the site is unshared, taken down or removed from the menu, /accounts opens elsewhere. The choice is kept, and it takes effect again when the member can open the site.
  • A member has one home. Choosing another replaces it.

​
Pin sites

A pin marks a site a member uses most. Each member has their own pins.
  • Pin with Pin a site to the member’s menu. The new pin goes after the member’s other pins. Unpin a site removes it.
  • A member has at most 50 pins. A stored pin counts toward the 50 even when the member can no longer open the site.
  • A member pins only a site their menu lists. That includes their own drafts. A site they removed from their menu is refused, and a site they can’t see is not found.
  • Pinning twice returns the pin that exists. That holds even at the limit.
  • A pin gives no access. A pin of a site the member can no longer open stays stored and shows in no menu until they can open the site again.
  • Order the pins with Order the member’s pins. It puts the sites you name first, in the order you send them, and leaves the other pins after them in their old order. Send 1 to 50 ids, each once. An id that isn’t one of the member’s pins is ignored.
  • Unpinning a featured site leaves it featured.
The menu marks each pinned site and lists the member’s pins, in their order, as pin_order.

​
Remove a site from the menu

A member can take a site they didn’t build out of their own menu. The site moves to the removed group.
  • Remove with Remove a site from the member’s menu. The menu entry of a removed site carries a removal_id. Put the site back with Restore a removed site.
  • A member can’t remove their own sites, or a company site the company requires. Both are refused.
  • A removal changes only the member’s menu. It doesn’t change the site for its owner, for anyone else it is shared with, or for who can open it by its address. It stays when the site is unshared and shared again.
  • A removed site isn’t pinned, featured or home. The menu lists none of them for it. They come back if the member restores it.

​
Feature sites for the company

A company admin can feature sites. A featured site is listed first, in the company’s order, in the menu of every member it is shared with.
  • Feature with Feature a site. Use Stop featuring a site to undo it, Order the featured sites to set the order, and List the featured sites to read it.
  • A company features at most 20 sites. Featuring a site that is already featured returns the feature that exists.
  • Only a published site can be featured. It can be the company’s or a member’s. A draft, a taken-down site, a site whose owner is no longer an active member and a branch can’t. A site that is featured and then taken down stays on the list, so an admin can stop featuring it.
  • Featuring shares a site with no one. A member sees a featured site only when it is shared with them. See Share a site.
  • Featuring writes nothing to the site. A member’s site keeps its version and history.
  • A signed-in admin features. A company API token can read the featured list but can’t change it.
The menu marks each featured site as pinned_for_everyone, and lists the company’s features in the company’s order as company_pin_order.

​
Know the limits

A company has no limit on the number of sites it owns.