Organizations today face a major problem:

They spend a ton of time managing access to all the tools & applications that contributors use

The bigger you are & the more tools you use, the worse this problem is

We propose a new solution: an interoperable organizational graph

🧵

We see organizational graphs as the foundation layer of internet-native organizations

An organizational graph holds all your roles and permissions data and makes it available to all the tools you use

Change your roles and permissions once, and see them updated everywhere

Organizations work better with Hats. Save time, automate onboarding, and manage permissions across the internet with programmable onchain roles

We see organizational graphs as the foundation layer of internet-native organizations

An organizational graph holds all your roles and permissions data and makes it available to all the tools you use

Change your roles and permissions once, and see them updated everywhere 

Your graph turns your organization itself into a digital object, *ready to be programmed*

This has big implications

It means that all of the properties of your organization and its individual roles can now be automated, just like any other software system

As the organizational graph protocol, we have three principles for building the best version of this infrastructure:

1.  Roles are the atomic unit of organizations
2.  The best graph integrates with all the tools orgs want to use
3.  The platform must be credibly neutral

1. Roles (aka "hats") bundle everything you want in an org graph: agents, responsibilities, permissions, accountabilities, comp & more

Roles are networked together with admin & accountability relationships so that power is always delegated to the right agents @ the right time

2. Hats Protocol is open source & leverages existing Ethereum standards to create elegant interfaces for composability.

This enables permissionless innovation — anybody can build new tools, applications, and businesses that leverage Hats organizational graphs.

Where the protocol really shines is by making every one of these components extensible and programmable

Orgs can use any criteria or logic to automate granting, revocation, accountability, and permissions delegation

https://docs.hatsprotocol.xyz/hats-integrations/eligibility-and-accountability-criteria 