Say you got an organization. Five people need to post as the company, so five people get the company password. Then one of them leaves. You need to reset the password and re-distribute. A year later nobody remembers who posted what.
Inkan does this differently, because delegation is the core primitive.
Your org has one identity: the master key, in cold storage. Each employee makes their own key, or you hand them a fresh one, and the org delegates signing authority to it. Marketing, support, the freelancer: each gets their own key.
From the outside it's one account, same name, same profile, same followers. Your employees speak for the org, each under their own key, but they don't disappear behind it: it's always on record who posted what.
The freelancer moves on? Revoke his key, effective immediately, nobody else gets touched. Goes rogue instead? Revoke, disavow the window, re-ratify what was legitimate.
One identity, many hands.
Live now on https://www.inkan.cc
Inkan does this differently, because delegation is the core primitive.
Your org has one identity: the master key, in cold storage. Each employee makes their own key, or you hand them a fresh one, and the org delegates signing authority to it. Marketing, support, the freelancer: each gets their own key.
From the outside it's one account, same name, same profile, same followers. Your employees speak for the org, each under their own key, but they don't disappear behind it: it's always on record who posted what.
The freelancer moves on? Revoke his key, effective immediately, nobody else gets touched. Goes rogue instead? Revoke, disavow the window, re-ratify what was legitimate.
One identity, many hands.
Live now on https://www.inkan.cc
4
