Exclusively Me

How exclusively.me and these tools work: the tool groups, how changes are proposed, previewed and approved, and the formatting and privacy rules. Call it first when unsure which tool to use.

Proposal: add rows to a page at a position (1 first, 0 last). For links prefer quickLink with what it takes in url. An address already on the page isn't added twice; one removed before comes back with its clicks.

Proposal: delete a sub-page (never the home page), only when the person asked. Its statistics stay; a new page at the same address brings it back.

One page: its header (title, bio, picture, hasAccessCode with its message and days), its look, and every row in order (id, kind, title, url, body, style, icon, isOn, schedule with scheduleFrom, scheduleUntil, scheduleDays, scheduleHours). Each row is what pages_save takes.

Before adding rows: the quick link types and what each takes (a handle, number or address), row kinds, styles, icons, the formatting rules, the plan's limits (with its timezone), and proFeatures: what Pro adds (scheduled rows, an access code, blocks, styles, themes), whether this plan has each, how to ask for it, and upgradeUrl. team_id 0 for the person's own pages.

The pages the person can change: their own (home first) and their admin teams'. Ids, addresses, live state and row counts.

Proposal: take rows off a page, only when the person asked. They keep their clicks and come back if added again. To hide a row instead, set isOn false with pages_save.

Proposal: a new order for a page's rows (row ids from pages_get; rows not listed follow in their order). Nothing is added or removed.

Proposal: a new sub-page (pageId 0, with slug and title; first ask whether they want a page on this account or a separate one, see help), or a page's header and rows. rows must be EVERY row in order: a row left out is removed. Send rows empty to change only the header (and the access code, Pro). Each row may carry a schedule (Pro). For small changes use pages_add_rows, pages_reorder_rows or pages_remove_rows. On a plan without a Pro feature asked for, the rest is proposed and a warning says how to upgrade.

Every sponsor the person posts about (their own and their teams'), with each platform's handle, hashtags, ad label and embargo. Read it before writing about a brand.

The person's OWN sponsors (not their teams'), in the shape sponsors_own_save takes, with how many their plan allows.

Proposal: one of the person's own sponsors, new (sponsorId 0) or changed. Send the whole sponsor; groups and showInMediaKit are a team's and are ignored.

Owners and admins. Proposal: put members in a group (usernames from team_members_list; a member can be in several groups).

Owners and admins. Proposal: a new member group, with its first members if given (usernames from team_members_list).

Owners and admins. Proposal: delete a group, only when the person asked. It is archived: out of every list, its members' time in it ends, its history is kept.

Owners and admins: the team's member groups, each with its groupId and its members' usernames. Read it before the other team_groups_ tools.

Owners and admins. Proposal: take members out of a group. They stay in the team.

Owners and admins. Proposal: a new name for a group. Its members, and the sponsors and message houses for it, stay.

Owners and admins. Proposal: the team's brand and media kit text. Send the whole brand as team_media_setup_get gives it. Logos are uploaded on the site.

Teams whose Media Centre the person can read (as a member or admin), with ids.

A team's media kit and brand as members see them: story, logos, colours, fonts, voice, hashtags, who is in the public kit, and the sponsors that apply to the person.

What the team wants said now, or at a moment: lead message, pillars, must and never say, hashtags, featured sponsors and embargoes, with the team's voice.

Owners and admins. Proposal: a message house, the always-on base or a dated campaign (messageId 0 for a new one). Send the whole house.

Everything to write one social post for a team on one platform, in one call, with a checklist. Use it first for any post about the team; ask the person only what happened.

Owners and admins: the team's brand, message houses and sponsors in exactly the shape the team_media_*_save tools take. Read it before proposing.

Owners and admins. Proposal: a team sponsor, new (sponsorId 0) or changed. Send the WHOLE sponsor as team_media_setup_get gives it; a field left out is emptied.

Owners and admins, with the Media Centre. Proposal: a member's role in the media kit, e.g. Captain. An empty role clears it. Who is in the kit is chosen on the site.

A team's members as its Members screen lists them: name, page, groups, role and media kit consent (mediaKitConsent, publicUse). Name, tag or picture someone in public only with consent. Owners and admins also get shared emails. group and search filter like the screen ('' for everyone).

Teams the person is an owner or admin of, with ids and addresses.

A page owner's custom themes, each page's look, and the allowed colours, fonts and button styles. Read it before themes_save or themes_use.

Proposal: make or change a custom theme (Pro; a team's: owners and admins), optionally putting it on pages. Only the fields sent change. To match a website, read it yourself and use its colours.

Proposal: the look of one page: a custom theme from themes_list, and the built-in look under it (dark, light, violet). No theme: the built-in alone.