Start comb docs, integrations, intro, organization

docs/documentation/getting-started/introduction.mdx

@@ -2,7 +2,8 @@
 title: "Introduction"
 ---
 
-Infisical is an [open-source](https://opensource.com/resources/what-open-source), [end-to-end encrypted](https://en.wikipedia.org/wiki/End-to-end_encryption) secret management platform that enables teams to easily manage and sync their environment variables.
+Infisical is an [open-source](https://opensource.com/resources/what-open-source), [end-to-end encrypted](https://en.wikipedia.org/wiki/End-to-end_encryption) secret management platform for storing, managing, and syncing
+application configuration and secrets like API keys, database credentials, and environment variables across applications and infrastructure. 
 
 Start syncing environment variables with [Infisical Cloud](https://app.infisical.com) or learn how to [host Infisical](/self-hosting/overview) yourself.
 

docs/documentation/getting-started/platform.mdx

@@ -2,10 +2,6 @@
 title: "Platform"
 ---
 
-Infisical is an [open-source](https://opensource.com/resources/what-open-source), [end-to-end encrypted](https://en.wikipedia.org/wiki/End-to-end_encryption) secret management platform that enables teams to easily store, manage, and sync 
-application configuration and secrets like API keys, database credentials, and environment variables across applications and infrastructure. 
-It also has secret scanning capabilities for detecting leaked secrets in codebases.
-
 This quickstart provides an overview of functionalities offered by Infisical.
 
 ## Managing your Organization
@@ -54,12 +50,6 @@ Here, developers can [override secrets](//project#personal-overrides), [version
 
 The integrations page provides native integrations to sync secrets from a project environment to a [host of ever-expanding integrations](/integrations/overview).
 
-<Tip>
-    Depending on your infrastructure setup and compliance requirements, you may or may not prefer to use these native integrations since they break end-to-end encryption (E2EE).
-    
-    You will learn about various ways to integrate with Infisical and maintain E2EE in subsequent quickstart sections.
-</Tip>
-
 ![integrations](../../images/integrations.png)
 
 ### Members

docs/documentation/platform/audit-logs.mdx

@@ -3,10 +3,25 @@ title: "Audit Logs"
 description: "See which events are triggered within your Infisical project."
 ---
 
-Audit logs record all actions going through Infisical including who performed which CRUD operations on environment variables and from what IP address. They help answer questions like:
+<Info>
+    Note that Audit Logs is a paid feature.
 
-- Who added or updated environment variables recently?
-- Did Bob read environment variables last week (if at all)?
-- What IP address was used for that action?
+    If you're using Infisical Cloud, then it is available under the **Team Tier**, **Pro Tier**,
+    and **Enterprise Tier** with varying retention periods. If you're self-hosting Infisical,
+    then you should contact team@infisical.com to purchase an enterprise license to use it.
+</Info>
 
-![Audit logs](../../images/activity-logs.png)
+Infisical provides audit logs for security and compliance teams to monitor information access. 
+With this feature, teams can track 25+ different events; 
+filter audit logs by event, actor, source, date or any combination of these filters;
+and inspect extensive metadata in the event of any suspicious activity or incident review.
+
+![Audit logs](../../images/audit-logs.png)
+
+Each log contains the following data:
+
+- Event: The underlying action such as create, list, read, update, or delete secret(s).
+- Actor: The entity responsible for performing or causing the event; this can be a user or service.
+- Timestamp: The date and time at which point the event occured.
+- Source (User agent + IP): The software (user agent) and network address (IP) from which the event was initiated.
+- Metadata: Additional data to provide context for each event. For example, this could be the path at which a secret was fetched from etc.

docs/documentation/platform/ip-allowlisting.mdx

@@ -3,6 +3,20 @@ title: "IP Allowlisting"
 description: "Restrict access to your secrets in Infisical using trusted IPs"
 ---
 
+<Warning>
+  IP allowlisting at the project-level is being replaced with IP allowlisting at the token-level now available with the Service Token V3 authentication method.
+  
+  Instead of providing trusted IPs (specific IPs and CIDR ranges) to be applied across all service tokens, 
+  you can now specify trusted IPs at the token-level.
+  
+</Warning>
+<Info>
+  Note that IP Allowlisting is a paid feature.
+
+  If you're using Infisical Cloud, then it is available under the **Pro Tier**. If you're self-hosting Infisical,
+  then you should contact team@infisical.com to purchase an enterprise license to use it.
+</Info>
+
 Projects in Infisical can be configured to restrict client access to specific IP addresses or CIDR ranges. This applies to any client using service tokens and
 can be useful, for example, for limiting access to traffic coming from corporate networks.
 

docs/documentation/platform/organization.mdx

@@ -5,37 +5,63 @@ description: "How Infisical structures its organizations."
 
 An organization houses projects and members.
 
-By default, Infisical creates an organization under your name. You can manage your organization in your organization settings.
+## Projects
 
-![organization name modal open](../../images/dashboard-name-modal-organization.png)
-![organization name modal open](../../images/organization.png)
+The **Projects** page is where you can view the projects that you have access to within your organization
+as well as create a new project.
+
+![organization](../../images/platform/organization/organization-projects.png)
+
+## Settings
+
+The **Settings** page lets you manage information about your organization including:
+
+- Name: The name of your organization.
+- Incident contacts: Emails that should be alerted if anything abnormal is detected within the organization.
+- SAML Authentication: The SAML SSO configuration of the organization (if applicable); Infisical currently
+supports Okta, Azure, and JumpCloud identity providers.
+
+![organization settings general](../../images/platform/organization/organization-settings-general.png)
+![organization settings auth](../../images/platform/organization/organization-settings-auth.png)
 
 ## Members
 
-Members of an organization can create and add other members to projects within that organization.
-
-To add a member to your organization, scroll down to the "Organization Members" section and invite the member via email. They'll receive an email to confirm their organization invitation. If the member is an existing user on the platform, they will be automatically added to the organization.
+The **Members** page is where you can manage members and their permissions within the organization.
+In the **Members** tab, you can add external members to your organization or remove them; you can also
+change their role.
 
 ![organization members](../../images/organization-members.png)
 
-<Note>
-  Note that access to projects must be provisioned to new members after they've
-  accepted their organization invitation, and they will not be added to any
-  projects by default.
-</Note>
+In the **Roles** tab, you can manage roles for members within the organization. 
 
-## Service Accounts
+<Info>
+  Note that Role-Based Access Management (RBAC) is partly a paid feature.
+  
+  Infisical provides immutable roles like `admin`, `member`, etc.
+  at the organization and project level for free.
 
-Service accounts represent machine identities such as VMs or application clients that can authenticate with Infisical. They can be provisioned read/write permissions for project(s) and environment(s).
+  If you're using Infisical Cloud, the ability to create custom roles is available under the **Pro Tier**. 
+  If you're self-hosting Infisical, then you should contact team@infisical.com to purchase an enterprise license to use it.
+</Info>
 
-To add a service account to your organization, scroll down to the "Service Accounts" section and create a service account. Afterwards, you can press on the edit button beside the service account to provision it permissions.
+![organization roles](../../images/platform/organization/organization-members-roles.png)
 
-![organization service accounts](../../images/organization-service-accounts.png)
+As you can see next, Infisical supports granular permissions that you can tailor to each role. So,
+if you need certain members to only be able to access billing details, for example, then you can
+assign them that permission only.
 
-## Incident contacts
+![organization role permissions](../../images/platform/organization/organization-members-roles-add-perm.png)
 
-Incident contacts of an organization are alerted if anything abnormal is detected within the operations of an organization.
+## Usage & Billing
 
-To add an incident contact to your organization, scroll down to the "Incident Contacts" section and add their email.
+The **Usage & Billing** page applies only to [Infisical Cloud](https://app.infisical.com) and is where you can
+manage your plan and billing information.
 
-![organization incident contacts](../../images/organization-ic.png)
+This includes the following items:
+
+- Current plan: The current plan information such as what tier your organization is on and what features/limits apply to this tier.
+- Licenses: The license keys for self-hosted instances of Infisical (if applicable).
+- Receipts: The receipts of monthly/annual invoices.
+- Billing: The billing details of your organization including payment methods on file, tax IDs (if applicable), etc.
+
+![organization usage and billing](../../images/platform/organization/organization-usage-billing.png)