Skip to content

Member & Client Quick Start

Kanbanomy overviewPremiumGet Kanbanomy →

For the people invited into a workspace, rather than the person who set it up.

There are two paths here. Pick yours:

If you administer the site, see the Site Owner Handbook instead.


Your workspace lives at /hub/ on the site. Ask your site owner for the exact link - they can rename it, and it may appear in the site menu as Hub.

The Hub shows you, and only you:

Section What it is
My Projects Projects you are a member of
My Tasks Tasks assigned to you across every project
My Submissions Projects you proposed, with their approval status
Overdue Tasks / Completed Tasks Your counts, not the team’s
Recent activity What changed in your projects
Upcoming milestones Deadlines coming at you

The Hub is personal. You will not see projects you are not part of - not because they are hidden from view, but because they are genuinely not readable by you.

There is also a Download my calendar (.ics) link. It subscribes your calendar app to your own milestones and due dates.

Click any project in My Projects. Inside, you get eight tabs:

Tab Use it for
Overview Description, dates, progress, team at a glance
Tasks The full task list, with filters and inline editing
Board Drag tasks between columns
Gantt The timeline view
Calendar Due dates and milestones by month
Milestones The bigger checkpoints
Activity Who did what, and when
Team Who else is on this project
  1. Find it. Hub to My Tasks, or the project’s Tasks tab.
  2. Open it. Click the task anywhere: the task panel opens beside the page (a full-screen sheet on phones) with every field, comments, files and time.
  3. Change its status. To Do, In Progress, Done. The project’s progress bar and everyone’s Hub update from this.
  4. Comment. Type @ to mention a teammate - they get a notification. Someone who is both the assignee and mentioned gets one notification, not two.
  5. Log time. Start the timer, or enter minutes manually with a note.
  6. Attach a file. Drag it onto the task. Attachments go to the site’s media library and are covered by its normal backups.

Everything you do lands in the project’s Activity tab under your name.

If your site owner has given you permission, the Hub shows + Create New Project.

What happens next depends on a setting the owner controls:

  • It goes live immediately, or
  • It enters an approval queue. You will see it with a banner reading “This project is awaiting approval. Only you, project members, and administrators can see it until it is approved.”

That banner is normal, not an error. Your project exists, you are its owner, and you can keep working in it. It is simply not visible to the wider team yet. Track it under My Submissions.

If it is declined, the banner becomes “This project was not approved. It is only visible to you, project members, and administrators.” Ask whoever reviews projects on your site.

You cannot approve your own project, even if you created it. That is deliberate.


You have been given access to one or more projects. You can see the work, follow progress and comment on tasks. You cannot change the work itself, so nothing you do can break a project.

  1. You receive an invitation from the project’s owner.
  2. You need a login. Your access is tied to a user account on the site. If you did not set a password when invited, use the site’s Lost your password? link with the email address the invitation went to.
  3. Log in, then go to /hub/. That is your portal. Ask your contact for the exact address if it is not in the site menu.

Your Hub lists the projects you were added to. Open one and you get its Overview, Tasks, Gantt, Calendar and Milestones tabs. Some tasks may be kept for the team only; you will not see those.

Open a task and use the comment box to ask a question or give feedback. The people working on the task get an email. Type @ to mention someone on the project team. You can edit or delete your own comments.

Every other editing control is absent: no status buttons, no timer, no dates to change. You can comment, and change nothing else.

This is enforced in two places, not just hidden in the interface - the pages omit the controls, and the API refuses the write even if a request is crafted by hand. There is nothing you can click that will damage the project.

If you need something changed, tell your project contact.


Most confusing moments have the same small set of causes.

A project you cannot access returns a 404, exactly as though it did not exist: the site shows its “Page not found” page, and the API answers “Project not found”. This is deliberate: a “you are not allowed” message would confirm the project exists, which is itself a leak. A hidden task works the same way and answers “Task not found”.

So a 404 usually means one of:

  • You are not logged in. Log in and retry the link before assuming it is dead.
  • You are not a member of that project. Ask the owner to add you.
  • The project is awaiting approval and you are not its submitter or a member.
  • You are logged in as the wrong account.

The link is probably fine. Check the first two before reporting it.

“Please log in to view your dashboard.”

Section titled ““Please log in to view your dashboard.””

The Hub needs a login. You are logged out, or your session expired.

“Permission denied or invalid request.”

Section titled ““Permission denied or invalid request.””

Usually a stale page. You left a tab open long enough for its security token to expire. Reload and try again. If it repeats immediately after a reload, you genuinely lack permission for that action.

Search and project lists only ever show what you are allowed to see. If a colleague can see it and you cannot, you are not a member of it yet - that is a membership question for the project owner, not a bug.

My Tasks lists tasks assigned to you. A task you created, commented on, or are simply interested in does not appear there. Open the project’s Tasks tab instead.


Two separate things decide what you can do. They are easy to confuse.

1. Your site-wide role - set by the site owner:

Role Can
Manage Administer everything, approve projects, change settings
Submit Create projects and work on tasks
View Read-only

2. Your role on each individual project:

Project role Can
Owner Full control of that project
Member Edit tasks, comment, log time
Viewer Read only

Both must allow an action. Being a Member on a project does not let you change site settings, and having site-wide Submit does not give you access to a project nobody added you to.

One more case: if your site owner made a project public, anyone can open it without logging in - but a visitor who is not a member sees only Overview, Gantt, and Milestones. The task list, board, activity feed, and team list stay internal to the project’s members. So a public project shares your progress without exposing the day-to-day working detail.