Your account
Settings, passwords, email changes, invitations and AI agents.
Open your account settings from Settings in the user menu, under your name in the header.
Notifications
The bell in the header shows how many notifications you have not read and opens the latest ones; All notifications lists everything. You are told:
- when a ticket you watch is created, commented on, changes status, is assigned or otherwise updated, never about your own changes;
- when somebody mentions you in a description or a comment (
@usernamein Markdown,[~username]in Jira wiki), whether or not you watch the ticket; - when an SLA clock breaches on a ticket assigned to you or that you watch;
- when a follow-up assigned to you in the CRM comes due.
You watch the tickets you create, report or are assigned automatically. A status change or an assignment that came with a comment is one notification, with the comment quoted if you may read it. While you are in Alba a new notification also appears briefly in the corner of the page. Opening a notification, or the ticket it is about, marks it read; Mark all read clears the rest. Stop watching a ticket to stop the notifications about it. Notifications are kept for a year, or for 90 days once read; what they reported stays in the ticket's history.
Every notification is also emailed, but not one message per change: email waits half a minute and sends everything that happened in that time as one digest, so several updates in a short time arrive as a single message with a link to each.
Answering by email
When the workspace receives mail (set up under Email), an email about one ticket says Reply to this email to add a comment at the top, and replying to it does just that: your reply becomes a comment on the ticket, under your name, with the history saying it came by email. Only the new text is kept; what your mail program quotes below it, and your signature, are left off, though the whole message is kept and View original email beside the comment downloads it. Files attached to the reply become the ticket's attachments, and pictures in the reply are shown in the comment. A reply longer than a comment holds (200,000 characters) is cut with a note saying so, and its whole text is attached to the comment as message.txt; a request sent by email is treated the same way. A member can make the reply an internal note by starting it with #internal. Someone following a request through its link answers the same way, and gets an account as if they had answered through the link.
A reply from an address nobody in the workspace has, or from someone who may not comment on the ticket, adds nothing; administrators see it under Email with the reason. A reply to a ticket that has since been archived, or sent to a reply address older than thirty days, gets a short automatic answer saying so, and an automatic reply of your own (out of office) never becomes a comment.
Email and password
Change your email address; a confirmation link is sent to the new address and the change applies when you follow it. Set a password if you would rather not use the emailed login links, and change it whenever you like. Changing sensitive settings may ask you to log in again first.
CRM logging address
If you work in the CRM and the workspace receives email, the account page shows your logging address: BCC it, or forward mail to it, and the message is logged on the contacts it concerns. Email and the CRM says what it does.
Invitations
Members (not customers) can invite people to create an account. Open Invitations from the user menu, or from the Manage invitations button at the foot of your account settings; the page takes an email address and a name, sends the link and lists the invitations still waiting to be accepted. Resend emails an invitation's link again when it was lost, with a new week to accept it (the old link stops working); Revoke withdraws it. Invitations are available while registration is open or invite only, and disabled when accounts come only from single sign-on. An invitation that carries a project makes the person a member with the role it names as soon as they accept, so only that project's administrators may send or resend one.
AI agents
Members can let AI agents such as Claude, ChatGPT or Cursor, and their own scripts, work on tickets for them. Manage AI agents at the foot of your account settings opens the page with the addresses to connect to, personal tokens and everything you have connected. It is there while an administrator has the REST API or the MCP server switched on for the workspace. See AI agents.