← All guides

Teams and workspaces · Taskending editorial team

Are Taskending settings personal or company-wide?

Understanding settings scope tells you whether a change affects only your account or the whole workspace.

· 1 min read

How to apply it

Manage language, notifications and connected sign-in accounts in personal preferences. Company settings contain members, roles and supported company configuration. For Git, Gmail and Teams, also check the specific project or company destination.

A concrete example

Your GitHub sign-in can be linked while the company repository remains unconfigured. Conversely, a company integration may be ready while your personal account still shows Connect. Those labels describe different objects.

What to watch for

When you belong to several companies, check the active company before changing settings. A personal preference does not necessarily apply to the entire team.

How to check the outcome

Read the account, company and project names before changing anything. Then verify that only the intended scope changed.

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.