What changed. What it means for your work.

Roles that match how your team works.

See workspace permissions in one matrix and build custom roles from an existing role on Business.

• View built-in and custom roles alongside the permissions they contain.
• Where supported, choose No access, Own only or Everything.
• Invite people onto workspace roles and see role names in the members list.
• Custom roles stay assigned after a downgrade; editing is frozen rather than deleting the roles.

Permission updates are being introduced in stages. Existing access checks remain in place; contact Neevio to confirm availability for your workspace.

Keep Slack threads with the task they discuss.

Connect Slack and link channel conversations to Neevio tasks when a message includes a task identifier.

• Slack connections now complete the OAuth exchange.
• Messages naming a task link the conversation thread to that task.
• Linked threads provide source pointers for Daily Updates and Knowledge Transfer.
• Updates posted by Neevio do not create duplicate task conversations.

DMs and private channels are not supported by this flow. Neevio stores thread pointers, not the message text.

Your day, written from the work you did.

Daily Updates bring completed work, ongoing tasks, blockers and waiting decisions into a short personal stand-up.

• Updates draw on task changes, comments, pull requests, documents, time records and approvals.
• Source links sit beside the statements they support.
• Follow-up questions help capture knowledge that task activity cannot explain.
• Answers survive an update being regenerated and stay separate from AI conclusions.

Updates are personal to the signed-in user. Weekly summaries are not generated yet; the dashboard decision panel remains labelled sample content.

A clear way to accept workspace invitations.

Existing users can find pending invitations, and email invitations lead to a page with an explicit accept or decline decision.

• View pending workspace invitations from the invitations page.
• Accept invitations to more than one workspace.
• Declining records the decision rather than leaving the invitation pending.
• The invitation screen flags when the signed-in email differs from the invited address.

Time records that follow you between devices.

Timesheets now store entries on the server, with task, activity and billable controls in the entry flow.

• Logged time is available across devices and in the review workflow.
• Starting a second timer stops and records the first timer's time.
• Mark an entry billable and choose its activity and task.
• Missing-time checks identify working days without entries, excluding weekends.

Stronger boundaries between tenant workspaces.

Tenant routing, sessions and database access now check that a request belongs to the correct tenant.

• Sessions are checked against the tenant where they were issued.
• If a dedicated workspace database is unavailable, access fails instead of opening data from another database.
• Activating a tenant requires its own database.
• Unknown and reserved subdomains are refused.

Tasks, sprints, epics and documents. Consistently.

The same names now appear across the interface, saved filters and API, alongside fixes to search and task relationships.

• Tasks, sprints, epics and documents use consistent names.
• Saved-view filters work with sprint and epic references.
• Global search, recent visits and task relationships received fixes.
• Removing tasks from a sprint records the activity.

Dedicated tenants with your own branding.

Deployment controls support tenant subdomains, an owned database, verified custom domains and sign-in branding.

• Provision tenants and migrate their schema into the configured database.
• Verify DNS for custom domains.
• Use a custom logo, headline and subtitle on the sign-in screen.
• Manage tenant requests and configuration from the admin panel.

These are deployment capabilities. Contact the team to confirm configuration and availability for your requirements.

Prepare handovers from the work and its context.

Knowledge Transfer collects the departing person's work context and uses it to prepare a structured handover dossier.

• Collect task descriptions, comments, changes and relevant documents.
• Extract decisions, gotchas and contacts into a structured record.
• Configured HRMS offboarding events initiate a session; active dossiers refresh overnight.
• Handed-over and acknowledged states require the departing person's and replacement's respective sign-offs.

AI-generated handovers still need human review. HRMS triggers and model access depend on configuration.

Plans organized around the work they support.

Plans group capabilities into core work, team operations, business intelligence and enterprise needs.

• Usage limits cover members, projects, tasks, storage and AI actions.
• Custom roles and field permissions belong to Business.
• Subscription billing uses Razorpay.

See the pricing page for current plan details; this entry records the September update.