Products
Services
Solutions
Regions
Industries Insights Case studies About Contact
For the IT approver

Permissions, data and what reaches Akora.

Timesheet runs in your SharePoint site and keeps its data in SharePoint lists there. This page lists every permission it asks for, where each piece of data lives, and the two calls the app makes to Akora.

DATA LOCATION
SharePoint lists in your site
SIGN-IN
Microsoft 365 (Microsoft Entra ID)
CALLS TO AKORA
Licence check and billing status
Questions? Contact support →

Permissions the app package asks for

When you enable the package in your tenant app catalog, SharePoint lists four API permission requests. An administrator approves them in the SharePoint admin center under Advanced → API access.

APIPermissionWhy Timesheet needs it
Microsoft GraphUser.Read.AllShows people by name: the names of project members, submitters and approvers, the people picker when an admin adds someone, and each person's manager and direct reports, which decide who approves whose week.
Microsoft GraphGroup.Read.AllLets an admin find Microsoft Entra groups by name when mapping a group to an admin role in the Admin roles section. Also lets Timesheet recognise owners of the site's Microsoft 365 group as site admins.
Microsoft GraphMail.SendSends the email when a week is submitted, approved or sent back. Timesheet sends each email as the person who acted, from their own mailbox, while they use the app. Timesheet sends no other mail. It does not read mail.
Akora Timesheet Vendor APILicense.ReadLets the app ask Akora whether your organization has a licence, and show the plan on the Billing page.

These are delegated permissions. The app uses them as the person who is signed in, in that person's browser, and can only do what that person could. Microsoft grants approved SharePoint Framework permissions to one shared SharePoint app that every SharePoint Framework solution in your tenant uses, so they apply to any such app, not only this one.

From Microsoft Graph, Timesheet looks people up by ID, searches people and groups by name, and reads a person's manager and direct reports. It does not write to your directory. The one thing it sends is email. When someone submits a week, their approvers get an email from that person's mailbox. When an approver approves a week or sends it back, the person gets an email from the approver's mailbox. These emails go through Microsoft Graph in your tenant, not through Akora. They show in the sender's Sent Items. Timesheet does not read anyone's mail. Before sending, it checks that the recipient has a mailbox (from their directory entry, with User.Read.All), and doesn't send to someone who hasn't. If you don't approve Mail.Send, Timesheet works and sends no email. Admin → Sent notifications shows each email it handed to Microsoft 365, or why it didn't.

The License.Read permission belongs to Akora's app, "Akora Timesheet Vendor API". For SharePoint to approve it, that app must exist in your tenant. After you buy or start a trial, a global administrator grants it admin consent from a link on the confirmation page. Microsoft's consent screen lists everything the app asks for. Read it before you accept.

Akora's service app asks for no application permissions. It cannot read your SharePoint sites, your directory or your mail on its own. The consent only creates the app in your tenant. That lets SharePoint approve License.Read, which the web part uses to check your licence with Akora.

Where your data lives

The first time someone with permission to manage the site opens the Timesheet page, the app creates its SharePoint lists in that site, as that person. Everything Timesheet stores is in those lists, including:

  • time entries, with their notes, billable flag and status;
  • clients, projects, tasks and activities, and who is on each project;
  • submissions, approvals and the reasons given when a week is sent back;
  • holidays, policy rules, delegations, admin-role mappings and workspace settings;
  • the emails it sent (to whom, with which template, when, and whether they went);
  • an audit log of changes made through the app.

The lists live in your tenant, under your site's retention and backup. Your site's permissions apply to them too, except where Timesheet locks a list (see Locked lists). People are stored by their Microsoft Entra object ID. The app reads names from Microsoft Graph when it shows them.

The app also keeps two small items in the browser. The first is the last licence it received, so a short outage at Akora doesn't stop work. The second is a note that the site's lists were checked in this browser session.

Who can see what

In its screens, Timesheet shows each person their own time. Approvers also see the weeks of the people they approve. Those are their direct reports in Microsoft Entra ID, and the members of projects they lead once they are approvers. Reports and CSV exports follow the same rule. Site admins are Timesheet admins and see everything.

That rule is enforced by the app, not by SharePoint. Anyone who can open the site can read Timesheet's lists directly, for example from Site contents, including other people's hours and notes (see which lists they can change). Use a dedicated site for Timesheet. Add only the people who log or approve time as members, not a wider audience.

Locked lists

Timesheet locks its own lists in SharePoint at the list level, never item by item. A site admin's first visit sets this up, and later admin visits check that the lists are still locked. Admin → Integrity shows when the lists were locked, by whom, which lists, and the last check.

  • Admin-only. Members and visitors can read these lists. Only the site's Owners and site collection admins can change them. The lists are Project members, Workspace settings, Admin roles, Delegations, Projects, Clients, Activities, Holidays, Policy rules, Email templates, Integrations and Admin audit.
  • Own items. Each person adds their own records and changes only those. These are Approval records, Audit trail and Email log.
  • Not locked. These are Time entries, Tasks and each person's week layout.

If a list can't be locked (no rights, or your tenant blocks it), Admin says which and why.

What the approval check guarantees

  • Forged approvals don't count. SharePoint records who wrote each approval, and members can't change that record. An approval counts only if the person it names wrote it and could approve that week when they did: a site admin, a project lead approver set up by a site admin, or the person's manager in Microsoft Entra ID.
  • Status comes from the approval records. Changing the status stored on a time entry changes nothing.
  • Changes after approval are marked. If an entry changes after its week was approved, the week, History, reports and the CSV say "changed after approval". Hours are never hidden.
  • Only site admins change who approves. A change to the approval settings by anyone else gives no approval rights until a site admin confirms it in Admin.

Admin → Integrity lists every approval that doesn't count or can't be checked.

Limits

  • Anyone who can open the site can read Timesheet's lists. Use a dedicated site.
  • An approval by a manager outside the person's own reporting line still counts, and Timesheet flags it for an admin to accept or reject.
  • Approvals made before the lists were first locked keep counting, marked "before verification".
  • If someone with owner rights unlocks Timesheet's lists, these protections pause until a site admin opens Timesheet again.
  • Site collection admins and the site's Owners are trusted.

Exactly what the app sends to Akora

The app makes two calls to Akora, both to https://api.akoracloud.com:

  1. Licence check, when the app opens and when an admin selects Check now on the Billing page. The request is GET /license?product=timesheet. The answer is a signed licence for your tenant. It gives the plan, its status and how long it is valid.
  2. Billing status, only when an admin opens Admin → Billing. The request is GET /me/subscription?product=timesheet. The answer is the plan, its status and its end date.

Each call carries one thing, a Microsoft sign-in token for Akora's API. The browser gets that token from Microsoft Entra ID. Microsoft puts your organization's tenant ID in that token, and details of the signed-in person such as their object ID and name. Akora's service checks the token and reads the tenant ID from it to find your licence. For each licence it issues, it records the tenant ID, the product, the plan, the licence it issued and whether the request came from a browser. It does not record the person's details.

No timesheet data is sent to Akora. The app sends no hours, notes, projects, clients, names or settings. Usage events the app records stay in the browser's developer console.

When you buy or start a trial

On the buy page you type your Microsoft 365 domain. Akora asks Microsoft's public sign-in service which tenant it belongs to, and shows you the tenant ID to confirm. Stripe handles payment and card details on its checkout page. Akora never sees your card. Akora keeps the subscription. That record holds your tenant ID and domain, the plan, its status and dates. It also keeps the billing contact from checkout, with your name, email and country.

Questions

Email support@akoracloud.com. The install guide shows where an admin approves each permission, and our privacy policy covers the website.