Settings

Settings on Diafunc live at two levels. Account settings control how you sign in, manage your credentials, and stay informed through notifications. They apply to you personally across every project. Project settings control a single project: who can see it, its default language, its members, and its programmatic access. This page describes both.

Your account is the identity you use to sign in to Diafunc. You can sign in with an email address and password, or through an external identity provider. Password changes and recovery, and connecting or disconnecting providers, are all handled from your account.

The Sign-in methods page lists the external identity providers connected to your account. Diafunc supports the following providers:

Provider	Status
Google	Connected (shows the linked email) or not connected
Microsoft	Connected (shows the linked email) or not connected
GitHub	Connected (shows the linked email) or not connected

For each connected provider you can Disconnect it from your account. To add a new provider, sign out and sign back in using that provider's button on the sign-in page; signing in with a provider links it to the account that shares its email address.

You can change your password at any time while signed in, and if you ever lose access you can recover the account by requesting a reset link sent to your email address. General account details are managed from your account page. These flows are hosted on the dedicated Diafunc sign-in service, so following any of these links hands you off to that service and back again once you are done.

Both are on your account page. Cancel subscription keeps your plan until the end of the current billing period, then moves you to Free; you can reactivate before then. Delete my account in the danger zone is permanent: it cancels any subscription, deletes your projects, and erases your name, email and sign-in credentials. Billing and tax records are kept for the legally required period, stripped of anything that identifies you.

Both dialogs ask, optionally, why you are leaving, with a short list of reasons and a field for your own words. Nothing in it is required. The reason you give when deleting your account is kept without your name or email, so it stays after the account is gone.

Feedback in the More menu, in the footer and on the Community page opens a short form: a subject if you want one, and your message. It reaches the Diafunc team through the same queue as support requests, and it is open on every plan. Without an account, the same entries lead to the contact form with Feedback selected.

Now and then the dashboard asks one question in a small card in the corner: on your first visit, what you want to use Diafunc for, and later, how likely you are to recommend Diafunc to a colleague (at most twice a year). Each card can be skipped or closed, and it never blocks the page.

Diafunc keeps you informed through an in-app notifications centre. The bell icon in the top menu shows a badge with the number of unread notifications and, when opened, lists your most recent items. Each notification carries a short summary and a link that takes you straight to what it refers to; clicking an item marks it as read, and you can also mark everything read at once. Unread counts refresh automatically while Diafunc is open in your browser.

Notifications are raised for the events that matter across your account:

Notification	When it is raised
Project invitation	Someone invites you to collaborate on a project
Team invitation	Someone invites you to join a team
Analysis completed	An automatic analysis run finishes successfully
Analysis failed	An analysis run stops with an error
Support reply	The Diafunc team replies to one of your support requests
Credit threshold	Your credit balance crosses a notable threshold
Subscription event	Something changes about your subscription or billing
System message	Diafunc has an announcement or account message for you

See Credits for how the credit threshold and subscription notifications relate to your balance, and Team for how team invitations work.

Email notifications for analyses. A finished analysis run can additionally reach you by email. Tick Email me when the analysis finishes when launching an analysis, and Diafunc sends a summary to your account email when the run completes or fails: the analysis name, headline quality, duration, credits spent, and links that open the notebook or download the report (PDF). The choice is remembered per analysis, so re-runs behave the way the analysis was launched, and you can change it later without relaunching: the Lab's Analysis panel shows an Email me when a run finishes toggle that applies to every future run, manual or scheduled. Your account page carries the default for new analyses under Notifications. Turn it on there if you always want the email, and the wizard's checkbox will start ticked. Results themselves stay behind sign-in; the email only summarises and links.

Every project has its own settings, reached from the project's Settings screen in the Lab. The settings are organised into tabs, and only members with permission to edit the project can change them.

The main Settings tab holds the project's core configuration:

Option	Description
Visibility	Public makes the project readable by anyone; Private restricts it to its members.
Language	The project's default programming language (Java, Kotlin, Python, JavaScript or Scala). Every function in the project is evaluated in it unless the function sets its own language in the function settings. New projects start on Java.

The API Tokens tab issues project-scoped tokens for programmatic access. A token acts against this project through the API, the CLI and the MCP server, which is convenient for automation and scripts. See the API authentication page for the token format and how to send it. The token list shows each token's scopes, when it was created, when it expires, and when it was last used to authenticate a request (updated at most once an hour; a token that has never been used reads "Never"), so a forgotten token is easy to spot and revoke.

The Members tab manages who can access the project and what each person may do. You invite collaborators and assign them a per-project role that governs their permissions. See Project Members for the full list of project roles and how invitations work.