Skip to main content

Linked organizations

A university with several faculties, or a group with several brands, does not have to issue every credential from one account. POK Proof of Knowledge lets you link one main organization to several secondary organizations: each secondary organization keeps issuing credentials under its own identity, while the main organization sees every relationship in one place and can distribute credits to them from its own balance.

The same screen serves both sides of the relationship. What "Linked organizations" shows you depends on whether your organization is acting as the main organization, as a secondary organization, or as neither yet.

Open Linked organizations​

You need the Administrator role, on either side of the relationship: to invite a secondary organization, to accept or reject an invitation, or to unlink. The "Linked organizations" card only appears for Administrators, even though Operators can also open "Organization Settings" for other purposes. See Users and permissions for what each role can do.

  1. In the top navigation bar, click your organization's name, then click "Organization Settings".
  2. Open the "Preferences" tab and find "Linked organizations" under "My preferences".
  3. Click "Manage".

Share your invitation code​

If your organization is not linked to anything yet, and has not started acting as a main organization itself, "Linked organizations" shows "Your invitation code", with the help text "Share this code with a main organization so it can invite you as a secondary organization." Click "Copy code" to copy it. POK confirms with "Invitation code copied".

This code stops being shown once your organization links its first secondary organization or sends its first invitation. At that point it is acting as a main organization, so there is nothing left to invite it as a secondary organization for.

Invite a secondary organization​

  1. Open "Linked organizations" and click "Invite".
  2. Paste the other organization's code into "Invitation code".
  3. Click "Send request".

POK confirms with "Request sent", and the invitation appears under "Sent requests" labelled "Pending request". "Request sent" does not mean the code was valid. POK never discloses whether an invitation code exists, so you see the same confirmation whether you typed it correctly or not. Confirm with the other organization that they actually received your request before assuming the link failed.

To withdraw a request you are still waiting on, click "Cancel" next to it. POK confirms with "Request cancelled".

Accept or reject an invitation​

When another organization sends your organization a request, "Linked organizations" shows it under "Received requests", together with a line reading "Requested by [name]". While a request is waiting for your answer, this is the only thing the screen shows: your own invitation code and everything else stays hidden until you decide.

  • "Accept": the two organizations are linked immediately, and POK confirms it.
  • "Reject": the request is dropped, and POK confirms with "Request rejected."

A secondary organization can only have one main organization​

"A secondary organization can only be linked to a single main organization." If your organization already belongs to one main organization, it cannot accept a second invitation until it unlinks from the first one.

"Linked organizations" always shows "Your linked organizations":

  • If your organization is a secondary one, it shows "This organization is part of [the main organization's name]", with an "Unlink" button.
  • If your organization is a main one, it lists every secondary organization linked to it, each with its own "Unlink" button, or "This organization has no linked secondary organizations yet." if none are linked.

Either side can unlink at any time by clicking "Unlink" and confirming. Once the link ends, the secondary organization's invitation code becomes available to share again.

Transfer credits to your secondary organizations​

The page opens with a card reading "Transfer credits to your secondary organizations": "From your main organization you can distribute credits among your secondary organizations and track each operation in the history."

"Transfer credits" lives in the left sidebar, but only once your organization is a main organization with at least one secondary organization linked to it, and only for Administrators and Operators. See Introduction to the platform for the rest of the sidebar, and Credits for how your organization earns and spends them.

Seeing the item does not always mean you can use it. Only Administrators can actually open the page: if you are an Operator, clicking "Transfer credits" sends you back to the dashboard without transferring anything. Ask an Administrator of your organization to make the transfer, or to grant you the Administrator role.

Above the list of secondary organizations, the page shows your own organization's "Total credits", and below it, a card for each secondary organization with its own "Total credits" and its own "Transfer" button. Click "Transfer" on a card to send credits to that organization, or click the "Transfer" button at the top of the page to choose the destination yourself. Both buttons stay disabled while your organization has no transferable credits, and the one at the top also needs at least one secondary organization to be linked.

If your organization has no transferable credits left, the page shows "You've run out of credits" and that "You need credits to make transfers and approve requests", directing you to request them by writing to contact@pok.tech.

Send a transfer​

The transfer dialog has two steps: fill in the details, then confirm.

  1. Under "Destination organization", pick the "Organization" you're sending credits to. It's already set if you opened the dialog from that organization's own card.
  2. Under "Credit type", the only option today is "Blockchain Credits", the same credits used for Blockchain NFT credentials. Blockchain Verify credits, shown as "Hash" in your balance, cannot be transferred from here.
  3. Under "Amount to transfer", enter a whole number in "Amount", up to your available balance. Click "Continue".
  4. POK shows a summary of the transfer and asks you to confirm. Check "I understand this transfer cannot be reverted", since the transfer cannot be undone once it goes through, and click "Confirm".

The transaction history​

Below the credit cards, "Transaction history" lists every transfer your main organization has made, in a table with "Organization", "Date", "Status", "Credit type" and "Amount" columns. Since only Blockchain credits can be transferred today, "Credit type" always reads "Blockchain". Until you make your first transfer, the table shows "No transfers yet."

Each transfer has one of three statuses:

  • Pending: the transfer is still settling; the credits have not moved yet.
  • Completed: the transfer went through; both organizations' balances have already updated.
  • Rejected: the transfer did not go through.

A Rejected transfer is not something the receiving organization decided. Unlike an invitation to link organizations, a credit transfer has no accept or reject step on the receiving side: "Rejected" means the transfer itself failed, not that anyone turned it down.

The sidebar item is missing, or opening it sends you home​

  1. You are not an Administrator or Operator. "Transfer credits" is not shown to Readers at all.
  2. Your organization has no secondary organizations linked yet. The item only appears for a main organization with at least one secondary organization (see "Invite a secondary organization" above).
  3. You are an Operator. You can see "Transfer credits" in the sidebar, but opening it sends you back to the dashboard: only Administrators can actually transfer credits.

A transfer is marked Rejected​

This is not a decision the receiving organization made: a credit transfer has no accept or reject step on its side. Check the amount and the destination and try the transfer again.

The transfer fails for insufficient credits​

The "Amount to transfer" field is capped to the balance your organization had when you opened the dialog. If that balance changed afterwards, for example because another transfer went out in the meantime, confirming can still fail with "Not enough available credits." Close the dialog and open it again to see your current balance before retrying.