update codeowners and docs

Author: BTreston

.github/CODEOWNERS

@@ -41,6 +41,7 @@ crates/bitwarden-crypto/** @bitwarden/team-key-management-dev
 crates/bitwarden-exporters/** @bitwarden/team-tools-dev @bitwarden/team-platform-dev
 crates/bitwarden-generators/** @bitwarden/team-tools-dev @bitwarden/team-platform-dev
 crates/bitwarden-organization-crypto/** @bitwarden/team-key-management-dev
+crates/bitwarden-organization-invite-link/** @bitwarden/team-admin-console-dev
 crates/bitwarden-organizations/** @bitwarden/team-admin-console-dev
 crates/bitwarden-policies/** @bitwarden/team-admin-console-dev
 crates/bitwarden-send/** @bitwarden/team-tools-dev @bitwarden/team-platform-dev

crates/bitwarden-organization-crypto/examples/make_invite_key_bundle.rs

@@ -29,8 +29,8 @@ fn main() {
     let key: &InviteKeyData = bundle.dangerous_get_raw_invite_key();
 
     // 3. The second part is `InviteKeyEnvelope`. This is the invite
-    // key sealed (a.k.a. sealed) by the org key. `InviteKeyEnvelope`
-    // automatically serializes to `base64` when using serde,
+    // key sealed by the org key. `InviteKeyEnvelope` serializes to the
+    // Bitwarden EncString text format (`"2.iv|data|mac"`) when using serde,
     // `String::from(&inviteKeyEnvelope)`, or wasm abi serialization.
     let organization_wrapped_invitation_key: &InviteKeyEnvelope =
         bundle.get_sealed_invite_key_envelope();

crates/bitwarden-organization-crypto/src/wasm.rs

@@ -1,9 +1,10 @@
 //! The wasm module holds serialization/encoding needed wasm bindings for
 //! any types related to InviteKeyEnvelope. This means base64url for the
-//! InviteKeyData type, and  base64 for the InviteKey type. In order to minimize
-//! complexity, the actual  B64/B64Url encoding/decoding are limited to the
-//! `From<String>` and `FromStr`  implementations. All other serialization
-//! goes through String to simplify maintenance.
+//! InviteKeyData type, and Bitwarden EncString text format (`"2.iv|data|mac"`)
+//! for the InviteKeyEnvelope type. In order to minimize complexity, the actual
+//! encoding/decoding is limited to the `From<String>` and `FromStr`
+//! implementations. All other serialization goes through String to simplify
+//! maintenance.
 use std::str::FromStr;
 
 use wasm_bindgen::convert::{FromWasmAbi, IntoWasmAbi, OptionFromWasmAbi};