Your studio’s sites, and who can touch each one.

Access per site, not per account

Studios usually share one hosting login, one editor login and a password manager entry per client, and hope nobody leaves. In Devdwell each site has its own People list:

• OwnerDecides who has access and can remove anyone.
• Can edit and publishFor the lead on that site: change it and put it live.
• Can editFor a designer, a junior or the client: change it; someone else publishes.
• No accessEveryone else. They don’t see the site at all.

When someone leaves the team or a client relationship ends, remove them from the sites they had. Nothing else changes.

A review step that doesn’t slow you down

Publish to staging, send the private link to the client or the account lead, and publish to production after the yes. The dashboard shows which sites have changes waiting, so nothing approved sits unpublished. Staging vs production.

Everyone sees the same status

Because status comes from the hosting itself, not from who pressed which button, everyone on the team sees the same truth: live, changes waiting, or needs attention, and who published last. The dashboard.

Many hands, many tabs

Each person opens the sites they’re working on in tabs and describes changes in plain words, or edits the files directly if they code. Changes carry on in the background, so one person can move several small jobs along at once. Editing.

What Devdwell isn’t (yet)

Devdwell is in early access. It doesn’t include time tracking, invoicing, a content management system or client billing; keep the tools you use for those. It focuses on the sites themselves: where they are, what’s live, who can change them.

Questions