dilack.Getting your place in the conversation ready…
dilackENTERPRISEDILACK ENTERPRISE
A place for voice and text conversations with corporate identity, organization-owned servers, and dedicated rules for access, guests, and data.
Available through a contract and assisted rollout. Features are being validated before general commercial availability.
Personal accounts remain free. Enterprise uses an identity managed by the organization, and its corporate servers follow the policies in the contract.
DILACK ENTERPRISE
Teams can still find their conversations, while the organization decides who can join and how the space is administered.
SSO integration with Microsoft Entra ID or Google Workspace. The corporate session is separate from a personal account; the identity provider handles authentication and its MFA requirements.
SCIM provisioning and deprovisioning for Entra ID. The initial Google Workspace setup uses SSO with assisted account creation and removal until automated integration is validated.
Each Enterprise server belongs to one organization. The initial policy limits communication to that organization; external contact requires an explicit decision.
Beyond roles, the organization can control reading, posting, and joining voice for an individual or a role in each corporate channel.
People outside the organization need approval and an expiration date to join corporate servers. Their access can be revoked early.
The corporate console brings together identities, guests, SSO, and export of the organization’s administrative events.
01 / IDENTITY
Rollout starts with domain verification and identity-provider setup. Access requires an active contract and an enabled SSO connection.
Email is not the permanent identity key. Changing an email address should not create a second person in the workspace.
| Provider | Sign-in | User lifecycle |
|---|---|---|
| Microsoft Entra ID | Corporate SSO | SCIM with a stable directory identifier |
| Google Workspace | Corporate SSO | Assisted provisioning and removal in the initial phase |
02 / ACCESS CONTROL
The default is “organization only.” If external contact is allowed, exceptions still follow guest and channel rules.
Existing personal servers are not converted to Enterprise automatically. Content migration will require its own process.
A corporate server belongs to one organization and is linked at creation.
Specific rules govern reading, posting, and joining voice.
Approved access with an expiration date and revocation.
Enterprise calls require managed media infrastructure; immediate shutoff still needs validation in a real environment.
03 / DATA AND AUDIT
The initial proposal combines exportable administrative events with retention periods by data type. Final periods and legal holds belong in the contract.
Complete deletion of attachments, metadata, and backups is still being validated. We do not promise full erasure before checking the entire data lifecycle.
04 / ENTERPRISE PLAN
The initial commercial model considers active SSO connections, corporate servers, and contracted storage capacity. Pricing, overages, support, and billing terms are set in the proposal.
Automatic usage metering and invoicing are still in development. This page is neither a price list nor an automatic billing offer.
GETTING STARTED
We align on the organization, domains, server count, and external-access policy.
We record the data-processing agreement and verify ownership of the corporate domain.
We configure Entra ID or Google Workspace and test sign-in with organization members.
We create corporate servers, review permissions, and validate events before expanding access.
No. Corporate identity and servers are separate from a free personal account.
Automatically linking an existing personal server is disabled. Enterprise starts with servers created for the organization.
The initial policy blocks external interaction. The organization may allow exceptions; each guest needs time-limited approval.
Some features, including plugins and link-based meetings, stay disabled on Enterprise servers until they have their own access, audit, and isolation controls.
DILACK ENTERPRISE PARTNER
Meet Conexora, a Dilack Enterprise partner.
Open a ticket with your organization size, identity provider, and access and retention needs. The team can outline the rollout and a proposal.
Open an Enterprise ticket