Organization, workspaces and activities

Everything in Kadu belongs to an organization, and its tasks are arranged in three levels:

Organization                ← your company; has a Playbook
└── Workspace               ← a business domain (Finance, Collections…)
    └── Activity            ← a grouping (Receivables Settlement, Reconciliation…)
        └── Task            ← what Kadu runs
            └── Execution   ← each time the task runs

Level	What it is	Where it comes from
Organization	Your company in Kadu. It holds the contracted plan, the monthly cost cap, the time zone, the members and the Playbook.	Created by Kobana, or at sign-up through the GitHub App.
Workspace	A business domain. In the Playbook, each workspace is a plugin.	Created by the repository sync, one per plugin.
Activity	Groups similar tasks within a workspace.	Declared in each skill's task: block (task.activity); the sync creates any that is missing.
Task	A skill that can be run from the console, by a schedule, through the API or by an HTTP call.	A repository skill with a task: block.
Execution	One run of the task, with timeline, logs, pending items, files, result and cost.	Created on every run.

The repository rules the structure

Workspaces, activities and tasks come from the organization's Playbook and are updated on every push. The console shows this structure in Settings → Content, along with the skills that have not become tasks yet. To change the name of a task, its activity or the secrets it asks for, change the skill file in the repository. An edit made only in the console is undone on the next sync.

See Kadu Playbook and Sync.

Members and roles

Whoever signs in to the console is a member of the organization, with a role that defines what they can do. Permissions have the format agent.<resource>.<action>, for example agent.executions.run to run a task or agent.secrets.update to change a secret. The same roles apply to anyone using the API with a personal token.

Some screens also depend on what Kobana has enabled for the organization: without the permission, the screen is read-only or does not appear.