Organizations and Projects

An Organization is your company's account: its members, its sign-in settings and its audit logs. A Project is where data lives. Each Table, its commit history, and the grants that control who can read it belong to exactly one Project. Choosing Project boundaries well is mostly a question of who reads the data and what must change together.

An exampleCopy Anchor Link

A robotics company creates one Organization for its team. Inside it, the demo Project holds the frames Table that its fleet records, and a second Project holds the data of an experiment. The two Projects have separate names, separate grants and separate storage. Because a commit can only change one Project, nothing the experiment does can change what the fleet's training jobs read.

OrganizationsCopy Anchor Link

An Organization holds people and account settings, such as single sign-on and audit logs. Each member has one Organization role: owner, member or guest. Organization roles control account actions, such as creating Projects and inviting people. They do not by themselves give access to the data in a Project; a grant does that.

ProjectsCopy Anchor Link

A Project belongs to one Organization and holds:

• its resources, such as Tables and Locations;
• the commit history of those resources;
• the grants that control access to them;
• a storage location for the bytes of the data Spiral manages for it.

When you create a Project, Spiral generates its ID and makes you its admin. Authorization lists the other grants a new Project starts with.

Choosing a boundaryCopy Anchor Link

Put data in one Project when it must be committed together or is read by the same people. A commit can change several Tables in one Project at once, but it cannot span two Projects. Use separate Projects when data needs different access, different storage, or a history that moves independently.

ServicesCopy Anchor Link

• Organizations manages members, invitations, and account settings.
• Projects creates and deletes Projects.