Type: Function
Function: ME
Syntax: ME()
Description: Returns the current user's usernames, one per app they connected, as records carry them in their username fields (e.g. ["jdoe", "John Doe"]).
The current user is the person viewing the insight. Through the Keypup API or the MCP server, it is the person the API token or the MCP connection belongs to.
It is used to match records on the current user, with fields such as author_username or assignee_usernames. IS_ME, INCLUDE_ME and their opposites are shortcuts for the most common uses.
Usernames are matched as text. A user's usernames are the ones of the apps they connected to their Keypup account (see Managing app identities), one per app. Someone else with the same username in another app, or with the same display name in an app which identifies people by name, such as Jira or Bitbucket, also matches. A user with no app connected matches nothing. The is me filter of the insight designer matches the user's accounts exactly: prefer it when building an insight.
Sample usage:
IN(author_username, ME())returnstruefor the records the current user created.CONTAINS(assignee_usernames, ME())returnstruefor the records assigned to the current user.IN(author_username, ME()) ? "Mine" : "Others"as a dimension splits the records between the current user's and the others'.