Fynk holds the framework agreements, the statements of work and the signatures. It is the clearest example of the second axis: there is nothing to link, because the person is found from their own email.
One widget reads from Fynk, and a portal shows the ones you turn on.
Example data. In a portal these carry your customer's own numbers, read from the system when the page opens.
Fynk finds the agreements where the logged in person is a party. That means it works in an employee portal too, where there are no organisations at all.
Per personPaste an API key from Fynk. There are no records to link afterwards.
The key is stored encrypted and is not shown again after it is saved. Kilango reads with it on request and writes nothing back.