Organisation tags
🧪 Experimental. Organisation tags are new and may still change. Tell us what works and what does not.
An Organisation tag marks a QC Item as relevant to an organisation, for example because the organisation uses the test in its delivery or contribution specifications. A QC Item can carry the tags of several organisations.
Who sees them
Everyone. The tags are listed in the Organisations box on the QC Item page, also when you are not signed in.
You can find all QC Items tagged by an organisation with the Organisation
field of the Advanced Filter. The Items list Export (CSV, API v1 + Organisations)
button (for Editors, representatives and workflow managers) adds the tags as Organisation_<n> columns.
The tags are not part of the QC Item definition: they are not in the XML,
the Template exports or the API output. API v1 only accepts them as a filter
(organization[]).
Tags do not create versions
An Organisation tag belongs to the QC Item itself, not to one of its versions. Adding or removing one never creates a new version and never changes the status, so a published QC Item can be tagged without going through the editing workflow. Every change is recorded in the log, with who made it and when.
Who can set them
- An organisation representative can add or remove the tag of their own organisation, on any QC Item, whatever its status.
- A QC workflow manager can add or remove the tag of any organisation, on any QC Item.
- Nobody else. Editors no longer set Organisation tags in the QC Item edit form.
Representatives and workflow managers tag from the Organisations box on the QC Item page, or several QC Items at once from the Items list: under Advanced filters, choose the organisation under Organisation tag, tick Select Items by clicking their cards, click the cards (or Select all), then Add tag or Remove tag.
Select all takes every QC Item that matches the current filters, also the ones further down the list that are not shown yet; the counter shows how many of them are selected. The result says how many QC Items actually changed: an Item that already had the tag (or did not have it, when removing) is skipped.
Who manages organisations and representatives
QC workflow managers keep the organisations and their representatives. If you need an organisation added, renamed or merged, or a representative added or removed, ask a workflow manager, or send a request yourself (see below).
They find the list under Administration > Organisations. There they can:
- create, rename or delete an organisation;
- merge a duplicate or misspelt organisation into the right one: its tags and representatives move over and the duplicate is deleted;
- add or remove representatives, by e-mail address or username, on the organisation's page;
- handle the requests to become a representative, under Administration > Representatives.
Each organisation can list e-mail domains (for example bbc.co.uk) and the
company name spellings that arrive with the login (for example BBC R&D).
QC uses them to suggest people on the organisation page. A suggestion
grants nothing: a person becomes a representative only when a workflow manager
adds them.
Accepting everyone on an e-mail domain
On the organisation's edit page, a workflow manager can tick Accept everyone
on these e-mail domains as representatives. Then every active account whose e-mail
address ends in @ plus one of the listed domains represents the organisation,
existing accounts and accounts created later alike. The domain must match
exactly: bbc.co.uk does not cover news.bbc.co.uk (list that one too if
needed). The organisation page lists these people under Representatives.
They cannot be removed one by one: untick the option or remove the domain.
It is off by default.
Asking to represent an organisation
Your My data page (user menu, top right) shows the organisations you represent, and whether a workflow manager added you or it comes from your e-mail domain.
To become a representative, click Ask to represent an Organisation there. Choose the organisation from the list or, if it is not there, type its name, and add a note for the workflow managers if you like. The QC workflow managers get an e-mail, and the request waits for them under Administration > Representatives, with a yellow count in the menu. A workflow manager approves it (with an existing organisation or, for a typed name, a new one) or rejects it, and you get an e-mail with the decision. Your requests and their status are listed on My data.
A representative whose account is deactivated or removed from the user list loses the right straight away. They stay on the organisation's list, marked as inactive, so a workflow manager can see who it was.
Implementers
Administration > Implementers lists the QC vendors whose people will confirm that a test can be implemented, grouped by company. Only workflow managers see this page. An Implementer is a normal user who belongs to one company; it does not give the QC editor role.
On this page a workflow manager can:
- add a company, rename it, or retire it (companies are never deleted);
- add e-mail domains to a company. A domain belongs to one company only, and
free-mail domains such as
gmail.comoroutlook.comare refused. Everyone who signs in with an address on the domain is linked to the company automatically. QC uses the address from the sign-in, never one a user types; - add or remove people by hand: pick an active editor from the list (it shows name, company and e-mail) or type an e-mail address or username. This wins over the domain: a person removed by hand is not linked again at the next sign-in, also when their address is on the company's domain. They are listed under Removed by hand; Link by domain again lets the domain link them again, at their next sign-in or with the button below;
- click Apply e-mail domains to existing users now to link accounts that already exist, without waiting for their next sign-in.
Removing a domain does not unlink the people it already linked.
Implementability confirmation
When an Item is Publication ready, the Implementers (people who belong to a company on the Implementers page and have at least the QC editor role) can confirm that the test can be implemented.
- On the Item page, an Implementer sees a button to confirm. There is only confirmation; nobody can reject. An Item that nobody confirms simply stays Publication ready.
- An Implementer can withdraw their confirmation until the Item is published, not afterwards.
- When two different companies have confirmed, the Item is published automatically. Two people of the same company count once.
- A confirmation belongs to the version it was given on. A new version of the Item starts without confirmations.
- Implementers get an e-mail when an Item becomes Publication ready and waits for them (see Notifications under your user menu; the setting is called As Implementer). Items > To confirm lists what they have not confirmed yet.
- Workflow managers publish by hand as before. They also see, on the Item page, who confirmed, for which company, when, and "n of 2"; Administration > Confirmations lists the Items that are waiting. Other users do not see who confirmed, or how many confirmations an Item has. The Publication ready e-mail to workflow managers says that the test waits for confirmation, and they are told when an Item is published through confirmations.
The confirmations are kept as a record that the test can be implemented. Your My data page lists your own.