Does Enclessa integrate with GitHub?

Yes. The GitHub module syncs issues into Enclessa board cards, attaches pull requests to the card they close, and surfaces check results. Writing changes back to GitHub is a setting each organisation enables deliberately.

Does Enclessa have an API?

Yes. Every capability is available over a documented OpenAPI surface, with bot accounts and personal access tokens scoped to specific operations, plus incoming webhooks and custom slash commands for lighter integrations.

Can I install third-party apps in Enclessa?

Not today. The marketplace carries first-party modules — Boards, GitHub, Time and People — and nothing loads third-party code at runtime. A partner catalogue is planned but does not exist.

Does Enclessa support single sign-on?

Not yet. Single sign-on through an external identity provider and SCIM user provisioning are planned enterprise work. Today accounts sign in with email and password, with multi-factor authentication for platform operators.

Core, plus the GitHub module

Bring the work in, without a second access model

Create your workspace See pricing

Enclessa integrates through four routes: a GitHub connector that turns issues into board cards and attaches pull requests to the card they close, incoming webhooks for anything that can post JSON, custom slash commands that call your own HTTP endpoint, and bot accounts with scoped personal access tokens against a documented OpenAPI surface. All four run on the same permissions as the rooms and boards they touch, so nothing needs an access model bolted beside the first one.

At a glance

GitHub: Two-way issue and pull-request sync (module)
Webhooks: Incoming, per channel
Commands: Built-in and custom HTTP slash commands
Automation: Bot accounts and scoped access tokens
API: Documented OpenAPI surface
Extensions: First-party modules only, no third-party code execution

What does the GitHub connector do?

Issues become cards on a Enclessa board and stay in step with the repository; pull requests attach to the card they close, and check results show up without opening another tab. Writing back to GitHub is a setting an organisation turns on deliberately, so a connector cannot start changing a repository because somebody moved a card.

Issues in, cards out, kept in sync
Pull requests attached to the card they close
Check results surfaced on the card
Pushing back to GitHub is opt-in per organisation

How do I connect something we built ourselves?

Incoming webhooks post into a channel with no code on our side. Custom slash commands call an HTTP endpoint you control and render its reply in the room. For anything larger there is a bot account with a personal access token scoped to exactly the operations it needs, against an OpenAPI document that describes every route the platform has.

Incoming webhooks per channel
Custom slash commands calling your endpoint
Bot accounts with scoped tokens
An OpenAPI document covering the whole surface

Is there an app marketplace?

There is a marketplace, and today it lists first-party modules: Boards, GitHub, Time and People. An operator installs, configures, suspends or removes a module from one place, configuration is versioned so a bad change rolls back, and secrets are sealed rather than stored in the clear. Third-party apps are a plan and not a capability — nothing loads code at runtime, which is a security position rather than a missing feature.

One catalogue for the four first-party modules
Versioned configuration with rollback
Sealed secrets and health reporting
No runtime loading of third-party code

What this does not do

The GitHub connector requires the boards module, since the cards it syncs are board cards.
The marketplace ships first-party modules only. There is no partner catalogue and no third-party code execution.
Single sign-on through an external identity provider, and SCIM provisioning, are planned enterprise work and are not available yet.

Task boardsKanban boards that inherit the team’s roles and link back to the conversation the work came out of.Read more MessagingTeams, channels, threads and direct messages, with search, files and a permission model checked in the data layer.Read more PeopleEmployee records, an org chart, effective-dated history, documents with acknowledgements, and onboarding that actually creates the accounts.Read more

Questions

Integrations: 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.