?tab=, which is how the rest of
these docs send you to a specific one.
The tabs
Self-hosting with billing off? Every plan gate above passes, because your account reports
itself as ULTIMATE when no Stripe keys are set. So you see all of them.
Plans and limits has the rule.
Why a tab is missing
Two different reasons, and they are worth telling apart before you go looking for a bug. Your plan does not include it. Webhooks, Auto Post, Sets, Signatures and Developers are each gated on a plan feature. The tab is simply not rendered. Your role is not admin. Teams and Developers additionally require you to be an ADMIN or SUPERADMIN in the organization. This one catches people out, because a plan can include the feature while your own account still cannot open it. Those two tabs call admin-only endpoints the moment they mount, so showing them to a regular member would produce an error rather than a page. If a teammate can see a tab and you cannot, role is the likely difference rather than billing.Linking straight to a tab
Append?tab= and the tab’s key:
global_settings, language, teams, webhooks, autopost, sets,
signatures, api and approved_apps. Note that the Developers tab is api, not
developers. An unrecognised or unavailable key falls back to Global Settings rather than
erroring.
Where to go for each
Your API key
Developers tab. The key the CLI, MCP and the public API all use
Teams
Who you invite, and what each role can do
Auto Post from a feed
One check takes one item, which is the thing to know before setting it up
Webhooks
What she sends, and what happens when your endpoint is slow
Sets and signatures
Saved channel groups and the text appended to posts
Notifications
What she tells you about, and where it arrives