Manthan — how to use the work suite
Everything your organisation needs to communicate and get work done, behind a single login. This page covers the two tools — Chat and Projects — and the bot that links them. Keep it bookmarked.
◆Getting started
The suite lives at work.devnullx.com. That page is your home — it shows the clock and every app available to you. Right now that's two apps:
| App | What it's for | Address |
|---|---|---|
| Chat | Talking to your team — channels and direct messages | chat.work.devnullx.com |
| Projects | Tasks, sprints, and tracking what's actually getting done | pm.work.devnullx.com |
work.devnullx.com addresses. Never use a raw IP address or a 100.64.x link — those are a different door and will keep asking you to log in.Chat is for communication. Projects is for tracking. Decisions and updates happen in Chat; anything that needs to be done and followed up lives as a task in Projects. Don't bury work items in chat scroll.
◆Logging in — once
You have one account for the whole suite. Log in a single time and every app opens without asking again.
- Open work.devnullx.com and click an app (or go straight to it).
- You'll land on the Manthan sign-in page. Enter your email and password.
- A 6-digit code is emailed to you. Enter it. That's your two-factor step.
- Done — you're now signed in to Chat, Projects, and everything else in one go.
Getting an account
You can't self-register. Your COO or an admin sends you an invitation email; you click the link, set a password, and you're in — with access to every tool automatically.
▲Chat
Chat (at chat.work.devnullx.com) is where the team talks. It works like the messaging apps you already know — channels for topics, direct messages for one-to-one, plus reactions, mentions, and search.
Channels & direct messages
- Channels — shared rooms for a topic or team. You're automatically in your organisation's channels. Click one in the left rail to open it.
- Direct messages (DMs) — private one-to-one chats. Click a person's name to start one. Anyone can DM anyone in their org.
- Mentions — type
@nameto notify someone. They get a highlight even if the channel is muted. - Search — the magnifier finds any message you can see.
Your two organisations (DevNullX and Spacephilic) are kept separate: each has its own private space, so one org's channels don't show up for the other.
Threads & calls
- Threads — reply in a thread to keep a side-conversation from cluttering the main channel. Hover a message → "Reply in thread". Threads are optional; use them when a topic needs its own space.
- Voice / video — start a call from a channel; it opens a meeting room everyone in the channel can join.
- Files — drag a file into the message box to share it.
■Projects
Projects (at pm.work.devnullx.com) is where work is tracked. Each organisation has its own project. Inside it you have a backlog, a board, and sprints.
Tasks & boards
- User stories are the work items (we call them "tasks" in chat). Each has a number like
#4, a title, a status, and an assignee. - Backlog — the full list of what's planned. Drag items into a sprint to commit to them.
- Kanban board — columns (New → In progress → Done). Drag a card across as work moves.
- Assign yourself or a teammate so everyone knows who owns what.
Blockers
When a task can't move forward, mark it blocked with a reason. Blocked items are flagged so leads can clear them. Open a task → "Block" → write why. You can also do this straight from chat (see the bot below).
✦The bot — chat straight to Projects
You don't have to leave Chat to manage work. Type a command in any channel and the bot creates or updates the item in your organisation's project, then replies with a link. It always knows which org you're in, so DevNullX and Spacephilic items never mix.
Command reference
| Command | Does |
|---|---|
!task <title> | Create a task |
!bug <title> | Create a task tagged as a bug |
!list | List open items in your org's project |
!mine | List the open items assigned to you |
!done <ref> | Close a task, e.g. !done 4 |
!block <ref> <reason> | Mark a task blocked, with a reason |
!unblock <ref> | Clear the block |
!rm <ref> | Delete a task |
!help | Show the commands |
ref is the task number the bot gives you when it's created, like #4 — use just the number: !done 4.
!task, !bug, !list, !mine); managers and above can close and block (!done, !block, !unblock); executives / COO can delete (!rm). If you lack permission the bot tells you.Examples
!task Prepare the Q3 board deck
→ ✅ Task in devnullx → Prepare the Q3 board deck (#4)
!block 4 waiting on finance numbers
→ 🚧 Blocked #4 — waiting on finance numbers
!list
→ Open in devnullx (2): • #3 Ship the demo 🚧 #4 Prepare the Q3 board deck
◆Adding people & organisations COO / Admin
Add a person to your org
- Go to auth.work.devnullx.com/admin.
- Create an invite — their email + role (employee / manager). They get an email, set a password, and are in every tool.
- Add them to your org's Projects project (Members) so they see tasks.
- Removing someone: deactivate them in the admin — they lose access to every tool within minutes.
Stand up a new organisation
Two steps need a platform admin (server side): creating the org in the auth system, and mapping its Projects project into the bot. Everything after that — inviting people, creating the project, creating channels — is done by that org's COO.
◆Troubleshooting
| Problem | Fix |
|---|---|
| It keeps asking me to log in / I'm logging in at a strange address | You opened a raw IP link. Always use the work.devnullx.com addresses. Log in once there; every app follows. |
| An app asks for its own code / OTP | You should only get the one email code at sign-in. If a tool asks separately, tell an admin — its own 2FA needs turning off. |
| I can't create a channel | By design — only the COO creates channels. Ask your COO. You can start DMs yourself. |
| The bot says it can't map me to an organisation | You're not in the roster yet. Ask an admin to add you. |
| I don't see tasks in Projects | You're not a member of the project. Your COO/admin adds you under Project → Members. |
| The bot didn't respond | Check the command spelling — it must start with ! (e.g. !task). Type !help to see them all. |