Administration

Running the organisation is a different job from opening a file.

Staff work in the portal. Administrators work in a console of their own, on the organisation’s host. People, identity, domain and storage stay off the file list a lawyer opens on Tuesday.

The Sessions table in the organisation console: each row shows who is signed in, a shortened session identifier, last used, and Revoke.
Sessions live in the organisation console. Revoke ends that sign-in; the file list a lawyer opens on Tuesday is a different door.

People and authority

Who is in, what they may do, and how they prove it.

People

Invite colleagues by the login they already have. Disable someone without deleting the history of what they did. There is always at least one organisation owner.

Groups

Put people in groups and grant folders to the group. When someone changes team, you change the membership — not fifty separate file permissions.

Roles you write

Core plans use the built-in roles. Business and Enterprise can define their own, so “matter lawyer” and “records officer” are real permissions, not nicknames.

Your sign-in

On Business and above, people keep the identity provider you already run. Password sign-in can stay on, or come off entirely if you only want federation.

Engagements and walls

Matters can carry extra restrictions. Ethical walls stop the wrong team seeing the wrong files even when they share an organisation.

Devices

Automation and scanners enrol as machines with their own certificates. Scripts do not borrow a person’s password. Enterprise can require that path for high-volume work.

The Audit screen in the organisation console: Verify chain, activity totals, a per-person breakdown of downloads, shares and uploads, and recent events.
The same console holds audit. Search who did what; verify the chain. Usage metres are a different screen.

How the product appears

Your name on the door. Your address if you want it.

Branding

Colours, mark and login appearance belong to the organisation. Recipients and staff see you, not a generic Casewelt skin, unless you prefer the default.

Your hostname

Use the Casewelt host we issue, or point your own name at it and prove you control the domain. Certificates are issued and renewed by Casewelt once the name verifies.

Mail from you

Invitations and share notices can leave through Casewelt’s mail, or through a mailbox you configure. Configuration never echoes the password back on a later read.

Capacity and where bytes live

Storage, quotas and the copy you keep in reserve.

Bring your own storage

Attach the object store your organisation already runs. Casewelt still moves every byte — nobody is handed a storage link. Leave it empty and Casewelt’s store is used.

Replica and disaster copy

Writes finish on the main store first. Casewelt can copy sealed objects to a second online site, and to a disaster archive you opt into. Clients never wait on the spare copy.

Quotas

Organisation totals and per-person ceilings. A person who would overflow is refused before the file is accepted, with a reason they can take to an administrator.

Share policy

Set the default and the ceiling for how many times an external share may be downloaded. New shares inherit the default unless someone raises it on purpose.

Usage and billing

See seats, storage, signatures and assistance credits in one place. Change plan when you are ready — the entitlements follow the subscription.

Help in the product

Administrators get a handbook and contextual help in English and Turkish. The public website is not the only place the product explains itself.

An afternoon

Someone leaves. The files must not.

Leave

You disable the membership. They cannot sign in. The audit still knows what they opened last month. You do not delete the person to make the risk go away — that would delete the evidence with them.

Join

A new starter joins a group, not fifty folders. The group already has the matter room. Custom roles on Business mean “records officer” can put a hold and cannot change billing. The owner cannot be the last one you disable.

Door

You point the organisation’s name at Casewelt and prove it. Recipients start seeing your address. Mail can leave from a mailbox you own; the password is never shown back on the next visit. Storage can be yours; Casewelt still carries every byte.

In a walkthrough

  1. Disable a membership and try that login. Then search audit for that person — the history must still be there.
  2. Move someone between groups and watch folder access change without re-permissioning files one by one.
  3. Read a storage or mail setting twice. The second read must not echo the secret.
  4. Attempt to disable the last owner. You want a refusal.

See the console

Walk the settings your security team will actually review.

Identity, domain, storage and roles — each one can be examined on its own, because they are not mixed into the file list.

Request a demo