Logging in to X-Author for Contract Advanced
Before you can work with your agreement documents in X-Author for Contracts Advanced, you must log in to your Salesforce org.
Prerequisite
The X-Author for Contracts Advanced add-in must be installed and added in Microsoft Word. For more information about installing the add-in, see Install Production X-Author for Contracts Advanced.
To log into X-Author for Contracts Advanced
You are logged into the X-Author for Contracts add-in.
If you encounter an OAuth error while logging into X-Author for Contracts on Microsoft Windows, refresh the page or re-enter your login credentials to log in.
|
Option |
Description |
|---|---|
|
User Name & User ID |
Displays the user name and ID |
|
Contracts |
Opens the contracts menu. |
|
Templates |
Opens the templates menu. |
|
Documentation |
Navigates the X-Author for Contracts Advanced documentation |
|
Technical Support |
Connects with the technical support team. |
|
App Details (earlier System information) |
Displays the system information that you are currently logged in to. |
|
Log Out |
To logout from the X-Author for Contracts |
Note that, on the login page, when you click Log In To Sandbox, you are taken to the Salesforce sandbox login page, where you must enter Sandbox credentials to log in.
To reload the X-Author for Contracts Advanced pane
To log out of X-Author for Contracts Advanced
-
Click the Home button (
).
- Click Log Out "<username>" to log out
To close and restart the X-Author for Contracts Advanced pane
- Log into X-Author for Contracts Advanced.
-
Click the Close button (
) on the right corner of the Task Pane to close the X-Author for Contracts Advanced pane.
- To reopen the X-Author for Contracts pane, click the X-Author Contracts ribbon in the Home tab.
When you reload/restart the X-Author for Contracts Advanced pane, all changes you made while working on the document are retained. You will not lose any information because of reloading/restarting.
Changing Orgs
Use Case: Switching Organizations to Manage Contracts Across Multiple Environments
This use case describes how users can switch between multiple organizations and set a default organization within X-Author for Contracts Advanced.
This use case provides an example of how to switch between organizations and set a default organization in X-Author for Contracts. Your implementation may vary based on your specific business requirements.
Business Context
Organizations using X-Author for Contracts Advanced often operate across multiple environments such as Production, Staging, QA, and Development. Contract administrators, legal teams, and sales representatives need the flexibility to work seamlessly across these environments without logging out and back in. By enabling organization switching and default organization settings within the application, businesses can streamline workflows, reduce administrative overhead, and ensure users always easily access their available environments.
Overview
This use case demonstrates how a user can switch between multiple connected organizations and designate a default organization. The organization switching feature allows users to:
- View all available organizations from a centralized modal interface
- Switch to a different organization with a single click
- Set a preferred default organization that loads automatically upon login
- Identify the current and default organizations through visual indicators
Scenario
A contract administrator at a manufacturing company manages contracts across five environments: Production, Preview, Staging, QA, and Development. The administrator primarily works in the Production environment but occasionally needs to test new contract templates in the Staging environment. To optimize their workflow, the administrator wants to:
- Set Production as the default organization so it loads automatically upon login
- Switch to the Staging organization to test a new contract template
- Return to the Production organization to continue daily contract management tasks
Actors/Roles
- Contract Administrator: The primary user who manages contracts and needs to work across multiple organizational environments.
- X-Author for Contracts Advanced: The application that provides the organization switching interface and manages user preferences.
Prerequisites
- The user has valid credentials and is logged into X-Author for Contracts Advanced.
- The user has been granted access to multiple organizations by a system administrator.
- At least two organizations are configured and available in the system.
Steps to Set a Default Organization
To set Production as the default organization:
- Click the organization selector displaying the current organization name in the application header.
- In the Switch Organization modal, locate the Production organization in the list.
- Toggle the Set as default switch to the ON position for the Production organization.
- The system displays a "Default" badge next to the Production organization, confirming the selection.
- Click Close or click outside the modal to dismiss it.
Steps to Switch Organizations
To switch from Production to Staging:
- Click the organization selector in the application header. The current organization displays with a "Current" badge.
- In the Switch Organization modal, review the list of available organizations:
- Production (Current, Default)
- Preview
- Staging
- QA
- Dev
- Click the Staging organization row.
- The system switches to the Staging environment. The organization selector now displays "Staging" as the current organization.
- The user can now perform contract management tasks in the Staging environment.
Result
- The Production organization is set as the default and will load automatically on subsequent logins.
- The user successfully switches to the Staging organization to test new contract templates.
- Visual indicators (Current and Default badges) clearly identify the active and preferred organizations.
- All contract data and settings reflect the selected organization's environment.
Next Steps
- After completing testing in the Staging environment, repeat the switching process to return to the Production organization.
- If workflow requirements change, update the default organization by toggling the Set as default switch for a different organization.
Best Practices
- Set your most frequently used organization as default to reduce the number of clicks required to start working each day.
- Verify the current organization before creating or modifying contracts to ensure changes are made in the correct environment.
- Use non-production environments (Staging, QA, Dev) for testing new templates or configurations before applying them to Production.
Business Value
- Reduces time spent switching between environments by providing a streamlined interface.
- Minimizes errors by clearly indicating the current working environment.
- Improves user productivity by automatically loading the preferred organization on login.
- Supports compliance and governance by separating production and test environments.
