Skip to main content
Company account settings & audit logs

Learn how to navigate issues related to your company name in our system - its unique attributes & find out how to retrieve it if forgotten.

Updated over a week ago

Attributes of a Company Name

  • Every company name is unique and distinctive.

  • A company-name must consist only of ASCII characters, excluding spaces and the characters ":" and ".".

  • The company name is crucial as it is used to verify your account.

  • Once set, a company name cannot be altered. To acquire a different company name, you will need to register a new company.

For license transfers to your new account, please contact [email protected].

Note: Data migration between accounts is not supported

If You Forgot Your Company Name

  • If you find yourself unable to recall your company name, please contact via the Chat/Messenger bot or emailing [email protected]

  • We will get in touch to assist you in retrieving the necessary information.

Understanding Audit Logs on

Audit logs provide a comprehensive record of numerous changes and actions that

occur within your piplanning app account. These logs are invaluable for monitoring and analyzing user and system activities for security and compliance purposes.

Key occurrences tracked in audit logs include:

  • Create, Read, Update, Delete (CRUD) operations for stickies

  • CRUD operations for users and teams

  • Changes to stickies triggered by connected ALM tools

  • And many other events

Accessing Audit Logs

To download Audit logs

  1. Ensure you are an administrator.

  2. Navigate to Settings in the Cockpit.

  3. Download the audit logs as an xlsx file.

Reviewing Audit Logs




UTC timestamp of the event.


The internal service where the event was triggered.


The source of the change, if identifiable; can be '-', 'User', or 'ALM'.


The type of event, e.g., 'sticky_alter', 'authorized', 'user.jwt-revoke', etc.


Additional data related to the event, such as parameters or metadata.


The piplanning session ID, if applicable.


The object ID for specific object-related actions (e.g., Sticky-note).


The user ID of the individual who triggered the change, formatted as either <tenant-id>.<user-id> or <user-id>.


The board ID for actions related to a specific piplanning app board.

Authentication of a User:

  • Authentication events are recorded as 'service=authserver; action=authorized'.

  • The 'authid' can be used to trace further actions of that user.

  • Additional details like IP address and user-agent are available in the 'data' property.

  • Prior to the 'authorized' event, a 'user.login.success' event is recorded, listing the user's email and 'authid'.

Did this answer your question?