User & Organization Settings
Last updated
Last updated
The User and Organization Settings section serves as a place for managing both personal and organizational configurations within the Probe platform.
To access the User and Organization Settings, click on the user icon located in the top-right corner. This will open the landing page and replace the Platform’s navigation bar with the dedicated navigation for the settings section.
In the continuation of this page, we will provide detailed explanations for the features within the User and Organization Settings section.
When you’re done with the editing, click Leave Settings, located near the navigation bar, to exit the settings page.
You can also find the Logout option in the bottom of the navigation bar, if you wish to log out of your account.
Besides viewing the email address you registered with, the Account Settings page allows you to update your account password directly within the Probe interface.
Navigate to the .
Click the “Generate New Token +” button.
Provide Token Details.
Token Name: Assign a meaningful name to your token.
Description: Add a brief description for clarity.
Duration: Specify the token’s expiration period.
Once generated, the token will be displayed only once. Be sure to copy and securely store it immediately, as it cannot be accessed again.
Name
Partial Token Key (not the full key for security)
Created Date
Expiration Date
Delete Token Option
To add a user to your organization, navigate to User & Organization Settings (user icon on top right corner of the platform) and follow these steps:
Create the organization (if it hasn't been created already):
Invite the User:
Enter the email address of the user you want to invite.
Click "Invite". An invitation email will be sent to the user, prompting them to create a password.
Manage User Status:
In the Users table, you can view all users and their current status.
For users who haven’t created their password yet (status: Invited), you can either:
Reinvite: Send a new invitation.
Copy Invitation Link: You can copy the link and manually send it to the user.
The invitation link is expirable. If the user does not accept the invitation in time, a reinvite will be required.
If the invitation email isn't received promptly, check the spam folder.
You can view all available and installed integrations on the Integrations page within the Organization section.
Do not confuse organization integrations with target integrations, which link the Probe platform to its target.
After clicking "Install" for the Jira integration, you will be redirected to the Atlassian Authorization app. Here, the SplxAI Platform will request access to your Atlassian account. You will need to select the app you wish to integrate with, grant the necessary access permissions, and accept the privacy policy.
All tickets created by the SplxAI Platform will be displayed as if they were reported by the user who accepted the integration.
To integrate SplxAI Platform with ServiceNow, you will need the following information:
ServiceNow Instance URL
Provide the URL of your ServiceNow instance.
E.g., https://<your_instance>.service-now.com).
API Key
The API Key required for access to ServiceNow's APIs.
User ID
Your ServiceNow User ID.
All tickets created by the SplxAI Platform will be displayed as if they were reported by the user defined in the integration process. The incident will be posted in the Incident Management Module.
On the , the tokens table lists all previously created tokens with the following details:
Go to the page in the Organization section of the navigation bar. If you haven't already, make sure to create your organization within Probe by setting your organization’s name.
Next, navigate to the page.
work at the organization level, allowing the Probe platform to connect with various applications and tools (e.g., Jira for project management) for smoother integration with your existing workflows.
To learn how to generate API key, visit the .
To view your User ID after generating the API key, click the information button next to the User field on the API key page. For more details, refer to step 2.e. in the previously linked .
