1. Application and authorized use
Ascent Law LLC provides Ascent Django for authorized firm personnel to manage office workflows, matters and accounting. Subject to these terms and the firm's access policies, an authorized user receives a limited, nontransferable right to use the application for approved firm work. Permission ends when the firm withdraws access or the user is no longer authorized.
These terms do not grant access to another firm's or client's accounts and do not themselves create an attorney-client relationship, change an engagement agreement, or authorize a charge. Public payment functions, if enabled, must present the appropriate payer disclosures and authorization separately.
2. User responsibilities
Use only your assigned access. Protect authentication credentials and do not share passwords, authorization codes or tokens. Do not bypass permissions, invoice locks, financial-review requirements or other safeguards. Report suspected unauthorized access or inaccurate records to the system administrator.
Users remain responsible for choosing the correct matter, company, accounting date and approved transaction. Review AI-assisted drafts before relying on or sending them; AI output is not an accounting instruction or substitute for professional judgment.
3. QuickBooks and other connections
An authorized administrator may connect an approved QuickBooks Online company through Intuit's authorization process. The connector uses the Accounting API for permitted accounting functions. Connection alone does not activate exports, approve accounting mappings, change the import start date, or backfill history.
When separately enabled, qualifying receipts, Clio-origin credits/write-offs and finalized invoice charges may be recorded in QuickBooks. LawPay/8am handles payment processing; the QuickBooks connector does not use Intuit Payments to charge payment methods. Independent provider terms and agreements also apply.
Provider outages, permission changes and conflicting or incomplete records can delay or prevent synchronization. A pending or failed sync is not proof that no provider record exists. An uncertain write must be reconciled before creating another entry. Users must not duplicate payments or invoices to work around an unconfirmed result.
4. Disconnection and record preservation
An authorized administrator can request disconnection using the application's connection controls. Future exports are paused before the revocation request. If revocation is not confirmed, the connection remains held for review.
Disconnection does not delete previously created accounting records, undo a payment, terminate a separate provider agreement or another application's connection, or erase firm audit history. An operation already in progress may still finish and require reconciliation. Records remain subject to the firm's approved retention and preservation obligations.
5. Information and safeguards
Use of the application is subject to its approved privacy notice and the firm's confidentiality, access and records policies. Users may access or disclose information only for authorized purposes. The firm may restrict access or pause features to investigate errors, protect information or maintain the system.
6. Availability and support
Features may be unavailable during maintenance, provider interruptions or controlled rollout. Do not treat the application as the sole evidence that a payment completed or a filing, communication or accounting action occurred; use the applicable confirmation and review workflow.
For application support, contact your Ascent Django system administrator. The firm's main office is 801-676-5506, 8833 S Redwood Rd, Suite A, West Jordan, UT 84088. Include a support reference when available, not secret credentials or full client records.
7. Changes
The firm may update the application and these terms. The firm will determine the appropriate notice and acceptance process for material changes. Changes do not retroactively authorize an otherwise unauthorized payment or disclosure.