Organizations

Group projects and team members under organizations in TaskView. Manage access with organization-level roles - owner, admin, and member. Each organization has its own members, projects, and settings.

Organizations let you group projects and people together. Every project belongs to an organization, and every user gets a personal organization automatically on registration.

Types of organizations

Personal - created automatically for each user. Contains your personal projects. Can't be deleted.

Team - created manually. Use these to collaborate with other people. You can invite members, assign roles, and manage shared projects.

Creating an organization

Go to the Organizations page and click the + button. Enter a name - a slug will be generated automatically. You can change the slug later.

Roles

Each member of an organization has one of three roles:

RoleDescription
OwnerThe person who created the organization. One owner per organization. Can't be transferred, can't be removed
AdminCan edit organization settings, invite and remove members, change roles
MemberCan work in projects they've been added to, but can't manage the organization, view member list, or change settings

What each role can do

ActionOwnerAdminMember
View organization+++
Edit name and slug++-
View member list++-
Add members++-
Change member roles++-
Remove members++-
Create projects+++
Delete organization+--

Regular members don't see the Members tab and can't edit organization settings - fields are disabled for them. The Delete button is only visible to the owner.

Managing members

Only owners and admins can manage members. The Members tab is not visible to regular members.

  1. Open the organization
  2. Go to the Members tab
  3. Enter an email address and click Add Member

New members are added with the member role by default. You can change their role to admin using the role dropdown next to their name. Members can only be invited by email. The person needs to have a TaskView account with that email.

When a project member with the Manage users permission invites someone into a project, that person is automatically added to the organization as a member - even though only admins and owners can add members directly. This is by design: a person can't be in a project without being in its organization. The auto-added member gets the minimum role and can't manage the organization.

Removing members

Click the X button next to a member's name. They'll lose access to the organization and all its projects immediately. The owner can't be removed.

Projects and ownership

Any organization member can create a project inside the organization. When a member creates a project:

  • The project owner is set to the organization owner, not the person who created it
  • The creator is automatically added as a collaborator with full access to that project
  • The project belongs to the organization and follows its lifecycle - deleting the organization deletes all its projects

Deleting an organization

Only the owner can delete an organization. Click the Delete button in the organization settings footer. This removes the organization and all its projects permanently.

Organization vs project permissions

Organizations and projects have separate permission systems:

  • Organization roles (owner, admin, member) control who can manage the organization itself - settings, members, deletion
  • Project roles control what users can do inside a specific project - create tasks, edit statuses, manage Kanban, etc.

Being an organization admin doesn't automatically give you permissions inside projects. You still need to be added to each project and assigned a project role. See Roles and Permissions for project-level access control.

The member list API endpoint is restricted to owners and admins. Regular members cannot fetch the list of organization members.

Built with Nuxt UI • © 2026 Thank you Nuxt Team for this awesome UI library and for the template!