Give everyone in your organisation one list of their work
Your people work across Jira, Microsoft 365, Azure DevOps and more. OneTaskList puts each person’s tasks on one board and marks them done where they came from. Enterprise gives you a region of your own, set up the way your IT team wants: in our Azure or yours, with our app keys or your own, with single sign-on or an allow-list.
Built and run from Melbourne, on Microsoft Azure.
- Runs in•
- OneTaskList's Azure, Australia East
- Sign-in•
- Single sign-on through Acme's Entra ID
- App keys•
- Acme's own app registrations
- Secrets
- In the Key Vault of Acme's region
- AI
- Each person's own key, kept in their browser
- Seats
- 238 of 250 in use
- Billing
- One invoice for every seat
For your people
Nothing to migrate. Every team keeps its tools.
OneTaskList doesn’t replace Jira, Planner or Azure DevOps. It gives each person one place to see what’s theirs, and keeps the team tools accurate.
Connect what they already use
Each person links the tools they work in. Their assigned issues, flagged emails and Planner tasks arrive on one board.
Plan their day their way
They order, group and filter their work with their own columns, due dates, effort estimates and work-in-progress limits.
Finish it once
Completing a task marks it done in Jira, Planner or wherever it came from, so the team’s view stays current without anyone entering it twice.
Works with
- Outlook Email
- Outlook Calendar
- Microsoft To Do
- OneNote
- Microsoft Planner
- SharePoint
- Jira
- Confluence
- Azure DevOps
- GitHub
- GitLab
- Slack
- Trello
- Asana
- ClickUp
- Monday.com
- Todoist
- Dynamics 365
- Altus
Outlook Email
Outlook Calendar
Microsoft To Do
OneNote
Microsoft Planner
SharePoint
Confluence
GitHub
GitLab
Slack
Trello
Asana
ClickUp
Monday.com
Todoist
Dynamics 365
AltusYour choices
Set it up the way your IT team wants
Every Enterprise customer gets a region of their own. How it runs is up to you: pick one option from each row. Your price follows what you choose.
Where does your region run?
In our Azure subscription
- We run everything, and the Azure cost is part of your price.
- Upgrades arrive with every release.
In your Azure subscription
- You pay Azure directly and can see every resource.
- We deploy and run it through Azure Lighthouse, a delegation you can withdraw at any time.
Whose app keys connect your tools?
OneTaskList's app registrations
- People connect their tools straight away.
- Each person approves the access, and you can revoke it in your admin centre.
Your own app registrations and secrets
- You register the apps in your own Entra ID, Atlassian and other admin centres.
- The secrets live in your region's Key Vault. Revoke an app and OneTaskList loses access to that tool.
How do people sign in?
Work accounts and an allow-list
- People sign in with their Microsoft, Google or GitHub work account.
- Only the addresses or domains on your list, such as *@acme.com, can join your region.
Single sign-on
- Sign-in goes through your Entra ID tenant, or any OpenID Connect provider with your own client ID and secret.
- Required for everyone on your domains, with sessions as long as you set.
AI keys are always yours.The assistant uses each person’s own provider key, stored in their browser, not on our servers. We never use your data to train models.
Whatever you pick, your region’s data, app and logs are used by nobody else.
Your region
A OneTaskList region that runs only for you
You get your own deployment in the Azure location you choose, in our subscription or yours. Your people still open OneTaskList at the usual address, and the shared front door sends them to your region. Only your people can join it, and nothing in it is shared with another customer.
Yours alone
Your Azure location- Container AppsThe web app and background sync
- SQL DatabaseBoards, people and connections
- Cosmos DBTasks
- StorageAttachments and queues
- Key VaultApp secrets and encryption keys
- RedisCache and live board updates
- Application InsightsLogs and telemetry
Shared OneTaskList services
- Sign-inAccounts, single sign-on and sessions
- OrganisationsMembers, seats and the audit log
- BillingYour invoices, issued by OneTaskList Pty Ltd
- Front doorWhere everyone opens OneTaskList. It sends your people to your region and keeps no customer data
Where your data lives
| Data | Where it’s kept | Leaves your region? |
|---|---|---|
| Boards, tasks, connections, tool tokens and attachments | Your region's SQL Database, Cosmos DB and Storage | No. Backups copy to Azure’s paired region; where that pair is outside your country, we keep them in-region instead. |
| Logs and telemetry | Your region's Application Insights | No |
| Names, emails and sign-in methods | Shared sign-in service | Yes |
| Organisation, seats, single sign-on settings and audit log | Shared sign-in service | Yes |
| Invoices | OneTaskList Pty Ltd, Australia | Yes |
| AI keys | Each person's browser | Never reaches us |
Task titles, notes, tags and connection tokens are encrypted in the database, with keys protected by your region’s Key Vault.
Your organisation
Seats, sign-in and leavers, handled
You decide who’s in. Joining, signing in and leaving all follow your rules, not each person’s.
Seats on one invoice
Buy the number of seats you need. People get one automatically the first time they sign in, while seats last. If you run out, nobody loses access and your admins are told.
Sign-in your way
With single sign-on, everyone on your domains signs in through your identity provider, and sessions end after 24 hours or any length you set up to a week. Without it, people use their work accounts and only your allow-list can join.
Leavers, cut off
Remove someone and their sessions end, their seat frees up, their connections stop syncing and they lose access to your region. Their data stays there, and we export it if you ask.
People already on OneTaskList
Someone with a personal account keeps their boards when they join. With single sign-on, they confirm before their account is linked to it, so nobody is moved without knowing.
An audit log
Every change to your organisation, its domains, its admins and its sign-in settings is recorded, with who made it and when.
Pilot first
Start with pilot seats for a fixed period. When the pilot is done, move to an invoice and open it up to everyone.
Getting started
From first call to everyone signed in
- 1
Scope
We agree your seats, your Azure location, and your choices for hosting, app keys and sign-in.
- 2
Sign-in
Send us your allow-list, or set up single sign-on: add OneTaskList to your Entra ID tenant, or give us an OpenID Connect client.
- 3
App keys
Use ours and skip this step, or create your own app registrations and share their secrets. We put them in your region’s Key Vault.
- 4
Your region
We deploy it in our Azure subscription or yours, connect it to the shared front door, and keep it up to date.
- 5
Pilot, then everyone
A pilot group goes first. Then everyone signs in with their work account and gets a seat.
Questions
What IT, security and procurement ask us
Data and security
Where is our data stored?
In your region, in the Azure location you choose: boards, tasks, connections, tool tokens, attachments and logs. Backups copy to Azure’s paired region, and where that pair is outside your country we keep them in-region instead. Names, emails, sign-in settings, seats and invoices are held by our shared sign-in and billing services.
What do you copy from our tools?
Enough to show each task: its title, link, status, due date, tags and a few details, and for some tools its notes. Titles, notes, tags and connection tokens are encrypted in the database, with keys protected by Key Vault.
Do you store passwords?
No. People sign in through your identity provider or with their Microsoft, Google or GitHub account, and each tool connects with OAuth.
Do you train AI on our data?
No. The AI assistant is optional and uses each person’s own provider key, which is stored in their browser, not on our servers.
Can we use our own app registrations and secrets?
Yes, if you want to. You register the apps in your own tenants and give us the client IDs and secrets, which we keep in your region’s Key Vault. When you rotate a secret, send us the new one, and if you revoke an app, OneTaskList loses access to that tool. Or use OneTaskList’s app registrations and connect straight away.
Can we run it in our own Azure subscription?
Yes. We deploy your region into a resource group you delegate to us through Azure Lighthouse. You pay Azure directly, we charge for the licence and for running it, and you can withdraw the delegation at any time, though we can’t support the region without it.
Do our people use a different address?
No. Everyone opens OneTaskList at the usual address and signs in, and members of your organisation are taken to your region. A custom domain isn’t available.
Identity and access
Do we need single sign-on?
No. Without it, people sign in with their Microsoft, Google or GitHub work account, and only the addresses or domains on your allow-list, such as *@acme.com, can join your region. You can add single sign-on later, and people keep their boards when you do.
Which identity providers do you support?
Microsoft Entra ID, and any provider that supports OpenID Connect, such as Okta, Google Workspace or Keycloak. SAML isn’t supported yet.
Do you support SCIM?
Not yet. People get a seat the first time they sign in, and removing someone in OneTaskList ends their access at once. If you disable them in your identity provider, they can’t sign in again, and their session ends within the length you set.
What happens when someone leaves?
Their sessions end, their seat frees up, their connections stop syncing and they lose access to your region. Their data stays in your region, and we can export it for you.
Can people keep using OneTaskList for themselves?
Yes. Boards someone already keeps in a public OneTaskList region stay theirs. Your organisation’s boundary covers your region.
Buying
How is Enterprise priced?
Per seat, plus your region. The price depends on what you choose: where the region runs, its Azure location and size, and how much of it we run for you. We quote after a short scoping call.
Can we try it first?
Yes. We can set up pilot seats for a fixed period before you commit to anything.
How do we pay?
We send your organisation one invoice for all its seats, on the schedule we agree. You can pay by card or bank transfer.
What support and SLA do we get?
Availability targets, backup retention and support hours are written into your contract, and you have a named contact at OneTaskList.
Tools
Which tools can people connect?
Outlook Email, Outlook Calendar, Microsoft To Do, OneNote, Microsoft Planner, SharePoint, Jira, Confluence, Azure DevOps, GitHub, GitLab, Slack, Trello, Asana, ClickUp, Monday.com, Todoist, Dynamics 365 and Altus. Gmail, Google Tasks, Notion, Salesforce and Zendesk are coming soon.
Does OneTaskList change anything in our tools?
It reads the tasks each person chooses to bring in. When they finish one, it updates that task’s status in the tool it came from. It doesn’t delete or reassign anything.
Let’s plan your rollout
Tell us a little about your organisation and we’ll come back with a plan and a quote. Pilots are welcome.
It helps to know
- How many people
- Which tools they use
- Where your data needs to live
- Your identity provider
OneTaskList, Level 15, 461 Bourke Street, Melbourne VIC 3000, Australia