What is the Zenkit Suite?
While any Zenkit product can be used as a completely separate product, they (and all future Zenkit products) are deeply connected with each other through the Zenkit Suite.
The Zenkit Suite is the collection of Zenkit products that work together seamlessly through the sharing of resources. Each product can be thought of as giving you a different perspective or way to work with the same data.
Say you've connected your Zenkit To Do with Zenkit Base:
Once connected, any change that you make to a task within a connected list will show within the equivalent Base collection, too, and vice versa. It's not that they 'sync' with each other, in fact, they're the exact same resource, just accessed using different apps. This is extremely helpful, especially if one person needs a general overview of all tasks with a structured approach such as a Kanban board or Gantt chart, and others simply need a simple and effective way to work through their tasks.
What are Resources?
Resources are the hierarchical objects you create and interact with within a Zenkit product. They are hierarchical because some resources contain other resources. In less abstract terms:
In Base, these are called "workspaces", "collections", and "items". In To Do these are called "folders", "lists", and "tasks". In Hypernotes, these are "notebooks", "notes", "blocks", and "tasks". These may go by other names in other Zenkit products.
In the end, an item in Base is the exact same resource as the task you see in To Do, Zenchat, or Hypernotes. The different apps just represent different ways to access, view, or work on the same resource.
Important terms to know:
Resource Owner - The resource owner is the product in which the containing resource was initially created (e.g. if you connect a collection in Base to Zenchat, Base is the resource owner, even if subsequent tasks/items are created in Zenchat). Currently it's not possible to change which product is the resource owner.
Containing Resource - A resource that contains other resources (e.g. a workspace contains collections, which contain items). Other Zenkit users may be added to containing resources as members (e.g. a list member in To Do, a notebook member in Hypernotes).
Usage quotas for each product in your account are based on the usage of resources that the product is the owner of, and that you also own.
For example, if you use Base and own several workspaces in which you've invited other people to collaborate in, those people are counted as members in your Base product quotas. Any items you create or files you add within collections in those workspaces will be counted towards your Base quota. If you've connected some of your collections to other products like Zenchat or To Do, any task you create there will still be counted towards your Base quota, as Base is the resource owner.
If you're a member of someone else's workspace in Base, then any resources added there will be counted towards their quota, not yours, as your account does not own the main containing resource.
If you've created a new folder in To Do and created new lists which you then connect to Base, then any tasks you create there are counted towards your To Do product quotas, as To Do is in this case the resource owner.
When you connect different Zenkit products with each other, you essentially gain a new way to view and interact with the resources in your account. The product in which the resource was originally created is the "resource owner".
For example, if you connect a list in To Do to Base, To Do will be the resource owner and the product by which quotas for that resource are calculated.
You connect products from the settings of a containing resource such as a notebook in Hypernotes or a collection in Base. Learn more about connecting products.
How many resources can I connect?
You can connect a different number of resources based on your plan:
Free: 3 connections
Plus: 30 connections
Business: 300 connections
Enterprise: 3000 connections
Click here to book a demo with our sales team and find the perfect plan for your needs.