v1.8.1-rc.7

Add platform plan to the billing page.

apps/documentation/pages/developers/public-api/reference.mdx

@@ -500,8 +500,35 @@ Now you can make a `POST` request to the `/api/v1/documents/{documentId}/fields`
   value, this is the value that will be used to sign the field.
 </Callout>
 
+<Callout type="warning">
+  It's important to pass the `type` in the `fieldMeta` property for the advanced fields. [Read more
+  here](#a-note-on-advanced-fields)
+</Callout>
+
 A successful request will return a JSON response with the newly added fields. The image below illustrates the fields added to the document via the API.
 
 ![A screenshot of the document in the Documenso editor](/api-reference/fields-added-via-api.webp)
 
 </Steps>
+
+#### A Note on Advanced Fields
+
+The advanced fields are: text, checkbox, radio, number, and select. Whenever you append any of these advanced fields to a document, you need to pass the `type` in the `fieldMeta` property:
+
+```json
+...
+"fieldMeta": {
+  "type": "text",
+}
+...
+```
+
+Replace the `text` value with the corresponding field type:
+
+- For the `TEXT` field it should be `text`.
+- For the `CHECKBOX` field it should be `checkbox`.
+- For the `RADIO` field it should be `radio`.
+- For the `NUMBER` field it should be `number`.
+- For the `SELECT` field it should be `select`. (check this before merge)
+
+You must pass this property at all times, even if you don't need to set any other properties. If you don't, the endpoint will throw an error.

apps/documentation/pages/users/_meta.json

@@ -10,7 +10,6 @@
   "signing-documents": "Signing Documents",
   "templates": "Templates",
   "direct-links": "Direct Signing Links",
-  "document-visibility": "Document Visibility",
   "teams": "Teams",
   "-- Legal Overview": {
     "type": "separator",

apps/documentation/pages/users/teams/_meta.json

@@ -1,5 +1,6 @@
 {
-  "general-settings": "General Settings",
+  "preferences": "Preferences",
   "document-visibility": "Document Visibility",
-  "sender-details": "Email Sender Details"
+  "sender-details": "Email Sender Details",
+  "branding-preferences": "Branding Preferences"
 }

apps/documentation/pages/users/teams/branding-preferences.mdx

@@ -0,0 +1,16 @@
+---
+title: Branding Preferences
+description: Learn how to set the branding preferences for your team account.
+---
+
+# Branding Preferences
+
+You can set the branding preferences for your team account by going to the **Branding Preferences** tab in the team's settings dashboard.
+
+![A screenshot of the team's branding preferences page](/teams/team-branding-preferences.webp)
+
+On this page, you can:
+
+- **Upload a Logo** - Upload your team's logo to be displayed instead of the default Documenso logo.
+- **Set the Brand Website** - Enter the URL of your team's website to be displayed in the email communications sent by the team.
+- **Add Additional Brand Details** - You can add additional information to display at the bottom of the emails sent by the team. This can include contact information, social media links, and other relevant details.

apps/documentation/pages/users/teams/document-visibility.mdx

@@ -13,9 +13,9 @@ The default document visibility option allows you to control who can view and ac
 - **Managers and above** - The document is visible to team members with the role of _Manager or above_ and _Admin_.
 - **Admin only** - The document is only visible to the team's admins.
 
-![A screenshot of the document visibility selector from the team's general settings page](/teams/team-general-settings-document-visibility-select.webp)
+![A screenshot of the document visibility selector from the team's global preferences page](/teams/team-preferences-document-visibility.webp)
 
-The default document visibility is set to "_EVERYONE_" by default. You can change this setting by going to the [team's general settings page](/users/teams/general-settings) and selecting a different visibility option.
+The default document visibility is set to "_EVERYONE_" by default. You can change this setting by going to the [team's general preferences page](/users/teams/preferences) and selecting a different visibility option.
 
 <Callout type="warning">
   If the team member uploading the document has a role lower than the default document visibility,

apps/documentation/pages/users/teams/general-settings.mdx

@@ -1,15 +0,0 @@
----
-title: General Settings
-description: Learn how to manage your team's General settings.
----
-
-# General Settings
-
-You can manage your team's general settings by clicking on the **General Settings** tab in the team's settings dashboard.
-
-![A screenshot of team's General settings page](/teams/team-general-settings.webp)
-
-The general settings page allows you to update the following settings:
-
-- **Document Visibility** - Set the default visibility of the documents created by team members. Learn more about [document visibility](/users/teams/document-visibility).
-- **Sender Details** - Set whether the sender's name should be included in the emails sent by the team. Learn more about [sender details](/users/teams/sender-details).

apps/documentation/pages/users/teams/preferences.mdx

@@ -0,0 +1,19 @@
+---
+title: Preferences
+description: Learn how to manage your team's global preferences.
+---
+
+# Preferences
+
+You can manage your team's global preferences by clicking on the **Preferences** tab in the team's settings dashboard.
+
+![A screenshot of the team's global preferences page](/teams/team-preferences.webp)
+
+The preferences page allows you to update the following settings:
+
+- **Document Visibility** - Set the default visibility of the documents created by team members. Learn more about [document visibility](/users/teams/document-visibility).
+- **Default Document Language** - This setting allows you to set the default language for the documents uploaded in the team account. The default language is used as the default language in the email communications with the document recipients. You can change the language for individual documents when uploading them.
+- **Sender Details** - Set whether the sender's name should be included in the emails sent by the team. Learn more about [sender details](/users/teams/sender-details).
+- **Typed Signature** - It controls whether the document recipients can sign the documents with a typed signature or not. If enabled, the recipients can sign the document using either a drawn or a typed signature. If disabled, the recipients can only sign the documents usign a drawn signature. This setting can also be changed for individual documents when uploading them.
+- **Include the Signing Certificate** - This setting controls whether the signing certificate should be included in the signed documents. If enabled, the signing certificate is included in the signed documents. If disabled, the signing certificate is not included in the signed documents. Regardless of this setting, the signing certificate is always available in the document's audit log page.
+- **Branding Preferences** - Set the branding preferences and defaults for the team account. Learn more about [branding preferences](/users/teams/branding-preferences).

apps/marketing/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@documenso/marketing",
-  "version": "1.8.1-rc.6",
+  "version": "1.8.1-rc.7",
   "private": true,
   "license": "AGPL-3.0",
   "scripts": {

apps/web/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@documenso/web",
-  "version": "1.8.1-rc.6",
+  "version": "1.8.1-rc.7",
   "private": true,
   "license": "AGPL-3.0",
   "scripts": {

apps/web/src/app/(dashboard)/settings/billing/page.tsx

@@ -41,7 +41,7 @@ export default async function BillingSettingsPage() {
 
   const [subscriptions, prices, primaryAccountPlanPrices] = await Promise.all([
     getSubscriptionsByUserId({ userId: user.id }),
-    getPricesByInterval({ plan: STRIPE_PLAN_TYPE.REGULAR }),
+    getPricesByInterval({ plans: [STRIPE_PLAN_TYPE.REGULAR, STRIPE_PLAN_TYPE.PLATFORM] }),
     getPrimaryAccountPlanPrices(),
   ]);
 

package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "@documenso/root",
-  "version": "1.8.1-rc.6",
+  "version": "1.8.1-rc.7",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@documenso/root",
-      "version": "1.8.1-rc.6",
+      "version": "1.8.1-rc.7",
       "workspaces": [
         "apps/*",
         "packages/*"
@@ -77,7 +77,7 @@
     },
     "apps/marketing": {
       "name": "@documenso/marketing",
-      "version": "1.8.1-rc.6",
+      "version": "1.8.1-rc.7",
       "license": "AGPL-3.0",
       "dependencies": {
         "@documenso/assets": "*",
@@ -438,7 +438,7 @@
     },
     "apps/web": {
       "name": "@documenso/web",
-      "version": "1.8.1-rc.6",
+      "version": "1.8.1-rc.7",
       "license": "AGPL-3.0",
       "dependencies": {
         "@documenso/api": "*",

package.json

@@ -1,6 +1,6 @@
 {
   "private": true,
-  "version": "1.8.1-rc.6",
+  "version": "1.8.1-rc.7",
   "scripts": {
     "build": "turbo run build",
     "build:web": "turbo run build --filter=@documenso/web",

packages/api/v1/implementation.ts

@@ -244,18 +244,10 @@ export const ApiContractV1Implementation = createNextRoute(ApiContractV1, {
       }
 
       const dateFormat = body.meta.dateFormat
-        ? DATE_FORMATS.find((format) => format.label === body.meta.dateFormat)
+        ? DATE_FORMATS.find((format) => format.value === body.meta.dateFormat)
         : DATE_FORMATS.find((format) => format.value === DEFAULT_DOCUMENT_DATE_FORMAT);
-      const timezone = body.meta.timezone
-        ? TIME_ZONES.find((tz) => tz === body.meta.timezone)
-        : DEFAULT_DOCUMENT_TIME_ZONE;
 
-      const isDateFormatValid = body.meta.dateFormat
-        ? DATE_FORMATS.some((format) => format.label === dateFormat?.label)
-        : true;
-      const isTimeZoneValid = body.meta.timezone ? TIME_ZONES.includes(String(timezone)) : true;
-
-      if (!isDateFormatValid) {
+      if (body.meta.dateFormat && !dateFormat) {
         return {
           status: 400,
           body: {
@@ -264,6 +256,12 @@ export const ApiContractV1Implementation = createNextRoute(ApiContractV1, {
         };
       }
 
+      const timezone = body.meta.timezone
+        ? TIME_ZONES.find((tz) => tz === body.meta.timezone)
+        : DEFAULT_DOCUMENT_TIME_ZONE;
+
+      const isTimeZoneValid = body.meta.timezone ? TIME_ZONES.includes(String(timezone)) : true;
+
       if (!isTimeZoneValid) {
         return {
           status: 400,

packages/ee/server-only/stripe/get-prices-by-interval.ts

@@ -12,10 +12,10 @@ export type GetPricesByIntervalOptions = {
   /**
    * Filter products by their meta 'plan' attribute.
    */
-  plan?: STRIPE_PLAN_TYPE.COMMUNITY | STRIPE_PLAN_TYPE.REGULAR;
+  plans?: STRIPE_PLAN_TYPE[];
 };
 
-export const getPricesByInterval = async ({ plan }: GetPricesByIntervalOptions = {}) => {
+export const getPricesByInterval = async ({ plans }: GetPricesByIntervalOptions = {}) => {
   let { data: prices } = await stripe.prices.search({
     query: `active:'true' type:'recurring'`,
     expand: ['data.product'],
@@ -27,7 +27,8 @@ export const getPricesByInterval = async ({ plan }: GetPricesByIntervalOptions =
     // eslint-disable-next-line @typescript-eslint/consistent-type-assertions
     const product = price.product as Stripe.Product;
 
-    const filter = !plan || product.metadata?.plan === plan;
+    // eslint-disable-next-line @typescript-eslint/consistent-type-assertions
+    const filter = !plans || plans.includes(product.metadata?.plan as STRIPE_PLAN_TYPE);
 
     // Filter out prices for products that are not active.
     return product.active && filter;