Does Enclessa include a kanban board?

Yes, as an optional module. Enclessa task boards are kanban boards owned by a team, using that team’s roles, with cards that link back to the conversation the work came from. An operator switches the module on per organisation.

Do Enclessa boards need separate permissions?

No. A board inherits the roles of the team that owns it, so the people who can see the team’s channels are the people who can see its board, subject to the same permission bits.

Can Enclessa boards replace Jira?

No, and they are not meant to. Enclessa boards deliberately have no dependencies, automation rules, cross-board views or reporting charts. They are for teams that want the work next to the conversation, not for portfolio management.

Module · switch on per organisation

Boards where the decision was made

Create your workspace See pricing

Enclessa task boards are kanban boards that belong to a team and inherit that team’s roles, so nobody administers a second permission model beside the first. A card links back to the channel and message the work came out of, which is the part a separate project tool cannot do. Boards are a module: they are off until an operator switches them on for the organisation.

At a glance

Availability: Module, off by default
Permissions: Inherited from the owning team
Linking: Cards reference the room and message they came from
GitHub: Optional two-way sync, requires the boards module

Why a board inside a chat platform?

Because the alternative is two access models, two invitation lists and two places to look. A board that belongs to a team already knows who may see it, and a card that references the message where the work was agreed keeps the reasoning attached to the task instead of stranding it in a channel nobody scrolls back through.

A board belongs to a team and uses its roles
Cards carry a link to the room and message behind them
Board changes can post into the channel that owns the work

What do the boards deliberately not do?

Enclessa is not a project management tool, and the boards are scoped so that they cannot slowly become one. There are no dependencies, no sub-items, no automation rules, no cross-board roll-ups and no velocity charts. A board is a shared list of work with columns and owners, and that is the whole of it.

No dependency graphs, no automation engine, no burndown charts
No portfolio or cross-board views
What was cut stays cut, and the reasoning is published

What this does not do

Boards are off until an operator enables the module for the organisation.
Dependencies, sub-items, automation rules, cross-board views and reporting charts are deliberately absent and will stay absent.
The GitHub connector requires the boards module, because its cards are board cards.

IntegrationsGitHub two-way sync, incoming webhooks, slash commands, bot accounts and scoped access tokens over an OpenAPI surface.Read more MessagingTeams, channels, threads and direct messages, with search, files and a permission model checked in the data layer.Read more Time trackingClock in and out, project time, timesheets with approval, absence with an entitlement ledger and an overtime balance.Read more

Questions

Task boards: common questions

Encrypted collaboration, hosted in Europe.

Create a workspace in a couple of minutes. It is yours at your-team.enclessa.app, hosted in the European Union, with encrypted direct messages from the first one you send.