Seat reassignment policy, the clause that survives the renewal.

The default policy.

The default Salesforce seat-reassignment policy is documented in the Master Subscription Agreement (MSA) and the product-specific Terms. The policy permits reassignment subject to conditions. The principal condition is the temporal condition: the original user must be inactive for a defined period before the seat can be reassigned to a new user.

The default temporal condition is the sixty-day inactive window. The condition is the Salesforce position, not a fixed contractual constant; the condition is negotiable on the MSA amendment. The wider MSA amendments worth fighting for spoke reads the amendment surface that includes the reassignment clause.

The sixty-day rule.

The sixty-day rule is the most common form of the temporal condition. The rule states that a seat can be reassigned to a new user only after the original user has been inactive for sixty days (the user has been deactivated for sixty days, not the user has not logged in for sixty days; the deactivation is the policy reference, not the inactive-login proxy).

The buyer-side counter is to negotiate the rule to thirty days or to remove it entirely. The thirty-day position aligns the reassignment cycle with the typical leaver-and-joiner cadence (the leaver is processed at the month-end payroll cycle, the joiner is onboarded at the start of the next month). The removal position is the strongest buyer-side outcome and is negotiable on the larger-account MSA.

The operational implication is the seat-holding cost in the inactive window. A leaver-arrival rate of twenty seats per month at a one-hundred-and-sixty-five-dollar Enterprise seat is an inactive-window cost of three thousand three hundred dollars per month under the sixty-day rule. The wider active-user audit spoke reads the inactive-cohort dynamic that connects to the rule.

The contractor exception.

The contractor exception is the policy clause that addresses the contractor and seasonal-workforce use case. The default Salesforce position requires a named-user seat for each contractor (the contractor is treated identically to an employee for licensing purposes). The position is operationally rigid in the contractor-heavy or seasonal-workforce context.

The buyer-side counter is to negotiate a shared-seat or floating-seat arrangement for the temporary workforce. The shared-seat arrangement licenses a pool of seats that can be assigned to multiple contractors over the contract year (with usage-rate limits to prevent abuse). The floating-seat arrangement licenses a smaller seat pool with a faster reassignment cycle (a same-day or seven-day reassignment).

The MSA amendment for the contractor exception typically specifies the contractor population size, the seat-pool size, the reassignment cycle and the audit-rights provision (the Salesforce right to verify that the shared-seat arrangement is not being used to disguise employee-population growth). The wider Order Form anatomy spoke reads how the contractor exception is recorded.

The M&A scenario.

The M&A scenario is the policy clause that addresses transferability. A buyer that acquires another organisation needs the Salesforce seats from the acquired entity to be transferable to the acquirer entity (the acquired company's contract becomes part of the acquirer's consolidated contract). A buyer that divests an entity needs the divested seats to be transferable to the divested-entity buyer.

The default Salesforce position requires consent to a transfer; the consent is at Salesforce's reasonable discretion but can be withheld in practice. The buyer-side counter is to negotiate a pre-approved transfer right that survives a control change without requiring Salesforce consent or a new purchase agreement. The MSA amendment specifies the transfer rights, the notice period, the carry-over of pricing and the carry-over of contractual terms.

The wider Salesforce inside an M&A transaction spoke reads the divestiture carve-out and the transferability geometry in detail.

The audit-rights envelope.

The seat-reassignment policy carries an audit-rights envelope. Salesforce reserves the right to verify that the reassignment policy is being respected (no over-assignment of seats, no parallel-use of seats by multiple users at the same time, no use of the contractor exception to disguise employee-population growth).

The audit-rights provision is the operational gate. The buyer-side discipline is the seat-assignment hygiene: the seat-by-seat assignment log, the deactivation-and-reactivation history, the contractor-pool usage report. The wider Salesforce FinOps spoke reads the ongoing discipline that produces the audit-defensible artefacts.

The renewal artefact.

The renewal artefact is the documented policy position: the MSA amendments that govern the reassignment rule, the Order Form notation of any seat-specific exceptions, and the operational evidence that the policy is being respected. The artefact survives the renewal because it sits in the MSA, not the Order Form; the MSA is the long-running agreement that the Order Form runs against.

The Admodum read on the seat-reassignment policy is the policy is the second-most-important clause in the MSA after the price-and-uplift clause. The reassignment policy governs the operational economics of the deployment over the contract life; the price-and-uplift clause governs the renewal-cycle commercial pressure. The wider seven-percent uplift spoke reads the renewal-cycle pricing context.

The wider active-user audit spoke reads the methodology that surfaces the seats available for reassignment.