Workflow tags (Stickers)


This article describes the Stickers concept of using the Trusted Twin platform. Stickers are a functionality to support workflows.

The purpose of this article is to provide system architects and developers with conceptual knowledge required to design solutions on the Trusted Twin platform. In order to consult developer resources, please go to the Trusted Twin docs website.

5 min read

Figure 1. Stickers on the Trusted Twin platform. 



Shared processes (i.e., processes involving multiple cooperating organizations) usually require two types of ownership – ownership of data and ownership of control.
Read more: Data access and visibility

The ownership of control is related to workflows. On the Trusted Twin platform, the ownership of control is supported via the Stickers functionality.

The Sticker functionality is inspired by sticky notes. A person can attach a sticky note to a surface and remove it afterwards.

Stickers support passing ownership of workflow items (e.g., tasks to be done) between multiple process participants. These participants are users identified directly by their user UUIDs or indirectly by their account or role UUIDs.

Figure 2. Sticker example.


On the Trusted Twin platform, Stickers are attached to Twins. One process participant (i.e., the Sticker creator) attaches a Sticker of a given color to a Twin. This Sticker can contain a note for another process participant (i.e., the Sticker recipient). The Sticker recipient removes the Sticker afterwards (e.g., when the task is completed).

Figure 3. Stickers in a workflow process.

Sticker recipients

When creating a Sticker, a user defines the recipients of the Sticker. The recipients list in the request body is a list of UUIDs (account, role or user UUIDs). Mind, that the recipients of a Sticker do not have to belong to the account where the Sticker was created. Only users who are the recipients of a Sticker can remove the Sticker.

Removing Stickers

The Sticker removal operation is atomic (i.e., only one user can remove a given Sticker). If a user tries to remove a Sticker after it has been removed by another user, they will receive a response stating that the Sticker does not exist.

Sticker validity

The validity of a Sticker is set upon creation of the Sticker. If the validity is set by a user, it cannot exceed one year. If a user does not provide the validity in the request, a Sticker is valid one year from the time of its creation .

Tips & tricks

  • If you require to retain the possibility to remove a Sticker you created yourself, you need to include your user, account or role UUID on the recipients list. If you don’t include your user, account or role UUID on the recipients list, you will not be able to remove the Sticker even if you are the user who created the Sticker.

For more information about how to use the Trusted Twin platform in your application’s architecture or technology stack, please contact or schedule a video consultation with us through Calendly.