Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Company logo and protected TLS co-branding. Add a verified company logo without replacing Technology Last Stop platform identity, ownership or backend controls. Current availability: Implemented for Professional and Enterprise. Before you start. A Professional or Enterprise Company Workspace and the Company portal manage permission. An authorized square company logo. Do not upload a partner, vendor or customer logo without permission. Step 1. Open Company > Portal settings > Company logo. Standard displays the upgrade boundary; Professional and Enterprise display the protected uploader. Step 2. Prepare a 512 × 512 pixel square PNG or WebP with a transparent or white background. JPEG is also accepted. The allowed range is 256–2,048 pixels square and the maximum file size is 2 MB. SVG, scripts and video are rejected. Step 3. Upload the file. The server verifies the declared type, binary signature, square dimensions, size and company scope before storing it in protected object storage. Step 4. Review the workspace header, navigation, cards and mobile layout. The company logo appears as an additive tenant identity. The official TLS logo and Technology Last Stop platform label remain visible and cannot be replaced through company settings. Step 5. Use Remove company logo to return to the TLS platform presentation. The change is revision checked and written to company Activity. The previous protected object is retained for recovery until lifecycle cleanup. Now verify the result. A Standard workspace cannot upload a logo through either the screen or API. A user from another company cannot read or replace the logo. The company image never replaces the TLS platform mark, owner controls or permission boundary. If you get stuck. Image rejected: export a true square PNG, JPEG or WebP; changing a filename extension does not change the image format. Logo looks small: remove unused transparent padding around the artwork while keeping the canvas square. Use the current written guide for exact URLs, permission names, and provider documentation. Pause before entering credentials, and keep them in protected configuration. I’m Nora, your TLS guide.