Members

Settings → Members (open Settings in the sidebar, then the Members tab) lists the people who can sign in to your organisation, their roles and what they can see. Only client admins see this tab and can make changes.

Invite a member

1. Under Invite a member, enter the Email and choose the Role. The hint below each role says what it may do; see also Roles.
2. For data providers, reviewers and country managers, set the Access limits: Whole organisation, or Only selected countries and assets and tick them.
3. Optionally set Access ends on for temporary access.
4. Click Send invitation.

The invitation link is valid for 7 days. People without an account also receive an email to set their password; they then set up their one-time password at the first sign-in. If your company uses single sign-on for its email domain, the page says so and no password is created for those people.

Change or remove a member

• Edit changes the role, the access limits or the end date.
• Remove takes the role away immediately. Their past work stays in the audit log.
• The organisation must keep at least one active client administrator, so the last one cannot be removed or given another role.

Reset a member’s two-step verification

When a member has lost their phone and their recovery codes, choose Reset two-step next to their name. Confirm who is asking first, for example by phone. The reset removes their authenticator app and recovery codes and signs them out; at their next sign-in they enter their password and set up a new authenticator.

It is not offered for your own account (use your account page), for people who are also members of another organisation (FEEC support resets those), or for people who sign in through single sign-on (their identity provider manages it). Each reset is recorded in the audit log.

Pending invitations

Pending invitations lists invitations not yet accepted. Re-send sends a new link (the previous link stops working); Revoke withdraws the invitation.

User limit

The page shows how many users you have against your plan’s limit, including pending invitations. External verifiers and executive viewers are free and do not count. Support access is granted on its own page, not here. See Support access and Plan & usage.

API keys

Settings → API keys (client admins only) manages the keys another system uses to work with your organisation’s data through the partner API. Each key has scopes, chosen when it is created:

• Read: assets, periods and the same aggregated results the dashboards show, for the whole organisation.
• Write activity data, Write events, Write site measurements: send monthly meter readings, flaring, venting, blowdown and well events, or site-level methane measurements. Data sent this way goes through the same checks as an Excel import or manual entry: locked months are refused, approved months are sent back to open, and every change is audited and recalculated.

A key with a write scope acts with the authority of the client admin who created it: the audit log shows the change as API key (created by …). The key stops writing if that person leaves the organisation or loses the right to enter data; reading is not affected. Give each key only the scopes it needs. Scopes cannot be changed later: create a new key and revoke the old one.

1. Under Create a key, enter a Name that says where the key is used, choose when it Expires (never, after 30, 90 or 365 days, or on a date you pick) and tick its Scopes (Read is ticked by default; at least one is needed).
2. Click Create key. The key is shown once: click Copy and store it in your system’s secret store. It cannot be shown again; a lost key is revoked and replaced.
3. Revoke stops a key immediately. A key also stops working after its expiry date.

The list shows each key’s first characters, its scopes, when it was created and last used, and when it expires, so unused keys can be found and revoked. Creating and revoking keys is recorded in the audit log. The full guide is API keys and the partner API. API access is part of some plans only: when your plan does not include it the page says so and links to Plan & usage; existing keys stay listed and can be revoked.

Webhooks

Settings → Webhooks (client admins only) tells another system when something happens, instead of it asking again and again. Each endpoint receives an HTTPS POST for the events it subscribes to: a period approved or locked, results recalculated, an import committed, a reconciliation decided, or LDAR surveys and repairs overdue.

1. Under Add an endpoint, enter the Endpoint URL (https only; addresses in private or internal networks are refused), an optional Description, and tick the Events.
2. Click Add endpoint. The signing secret is shown once: copy it into the receiving system. Every request carries the headers X-Webhook-Timestamp and X-Webhook-Signature (HMAC-SHA256 of the timestamp and the body with that secret), so the receiver can check that the request comes from your organisation and is recent.
3. Send test queues a test ping; Deliveries shows the delivery log with each event’s status, HTTP code, number of attempts and last error.

Failed deliveries are retried for a while. An endpoint that keeps failing is disabled after failures; fix the receiver and click Enable. Disable pauses an endpoint, Rotate secret replaces the signing secret (the old one stops working at once) and Delete removes the endpoint and its log. Webhook payloads contain identifiers and states only, never emissions values: the receiving system reads the details with a Read API key. Webhooks need API access in your plan, like API keys. See Webhooks for the events, signature check and retries.

Your notifications

Settings → Notifications is personal: it chooses which emails you receive from this organisation. Everything is on until you turn it off.

• Periods: a month waiting for your approval, or your submitted month sent back.
• Data due: the monthly reminder that data is due.
• LDAR reminders: overdue surveys and repairs.
• Import results: the result of your own Excel imports.
• Verification: RFIs and findings of verification engagements.

Turning data due or verification off also stops the matching notifications in the mobile app. Invitations, sign-in and security emails, and scheduled reports sent to your address are always delivered.

The notification centre

The bell in the top bar shows how many notifications you have not read; click it to open the Notifications page. It lists, newest first, what happened in this organisation that concerns you: a month submitted for review, sent back, approved or locked, a request for information raised or answered, your report ready, your import failed, a restatement approved, overdue LDAR items, and anomalies in your data. Click a line to go to the screen it is about (it is marked read), or use Mark read, Dismiss and Mark all read. Use Unread only to hide what you have seen.

The bell is separate from your email choices: turning an email off under Settings → Notifications does not remove the item from the bell. Anomalies are checked once a day over the last three complete months and reach administrators and methodology owners, and anyone who watches the asset (see Anomalies). Notifications are kept for 180 days.