← All guides

Teams and workspaces · Taskending editorial team

Do not forget work handover when removing membership

Offboarding involves more than removing access. Review open work, ownership and connections authorized by the departing person.

· 1 min read

How to apply it

Filter the person’s open issues in Taskending and assign new owners. Preserve company ownership continuity where relevant, then remove the appropriate membership scope. Personal sign-in links and company integrations remain different concerns.

A concrete example

The person may have authorized a Teams connection through their account. Removing membership calls for a separate delivery-continuity review. Open customer requests also need a new owner.

What to watch for

Removing company membership differs from removing someone from one team. Multiple subordinate membership events do not necessarily represent separate user actions. Read the scope before removal.

How to check the outcome

Verify the person cannot access restricted areas and transferred issues appear under their new owners. Test required integrations separately.

Try it in your own workflow.

Create a company workspace and your first issue. Taskending is currently free.

Start for free

Keep reading

01
Teams and workspaces

What to check when choosing a Jira alternative

Compare workflows, support, permissions and migration before choosing a free Jira alternative. Understand what Taskending supports and what it does not.

02
Teams and workspaces

How to start a free workspace

Begin with a small real workflow instead of moving every company process at once. Taskending is currently available without a credit card.

03
Teams and workspaces

How company, project and team differ

A company workspace defines an access boundary, a project organizes work context and a team organizes shared planning. They are more than interchangeable folder names.