For platform admins

A platform admin sees the same Sources and Packages screens as a knowledge editor, and uses them the same way. The difference is the altitude: you care about every customer organization, not one country’s next draft. Staff roles live on the internal Worklexia organization. A customer admin who invites a colleague as admin does not grant them.

Same screens, wider duty

• You can register sources, clear the inbox, and approve drafts. Follow Sources and the watch inbox.
• You can run coverage, batches, and registry work. Follow Country packages.
• You see the same platform assistant as a knowledge editor, including the count on Sources. Confirm still runs the step as you.
• You decide who may be a knowledge editor or another platform admin. That is not done from a customer Invite form.

When Advisory must pause everywhere

If Advisory needs to be turned off for every customer — for example while the library is unsafe — that is a platform-team step. There is no button for it on Sources or on a customer’s billing page. It applies to every organization at once. Customer admins will see Advisory is turned off on their threads, and new questions will not send. Turn it back on the same way. One customer’s plan limit is a different pause: that one stops only when that organization reaches its monthly questions or its payment fails.

Who gets a staff role

Staff roles sit on the internal Worklexia organization. A customer admin who invites a colleague as admin does not grant knowledge-editor access. If someone sees Staff role required and should not, grant the staff role on the internal side, then have them sign in again.

What you do not do on a customer org

Do not use a customer organization’s Members page to create staff. Customer admins manage their own seats and plan. You step in when the library or the whole service is at risk, not to pick a customer’s home country.