Cowork Arcetec: your team and AI working on the same thing.

Cowork Arcetec with Microsoft 365 is the AI-powered workspace from ARCETEC SOLUCIONES TECNOLÓGICAS SAS. The whole organization works inside it: projects are created, shared with the right people, and every conversation stays where the team can find it. The agent works on the information the company already has, with each person's delegated access: the SharePoint libraries it already uses as its repository and, if the organization turns it on, its Microsoft 365 email in read-only mode. Each project carries its destination folder, its brand, its instructions and its skills, so the team does not repeat the same context in every conversation. It produces five types of deliverable with the brand applied automatically: presentations in PDF and PowerPoint with native objects, A4 documents in PDF and Word, spreadsheets in Excel, diagrams in PNG and SVG, and code projects in twenty-nine languages. A search engine that combines text and meaning finds any conversation or project, and people sign in from a computer, tablet or phone with their corporate account. Files are archived in the company's SharePoint and never stop being yours. It integrates with in-house systems through MCP connectors and APIs registered by an administrator, with encrypted credentials. Artificial intelligence is included: Claude models in Microsoft Foundry, on Azure. It includes sign-in with Microsoft Entra ID, administrator and read-only profiles, and an audit log. Arcetec implements, integrates and supports the platform from Cajicá, Cundinamarca, for companies in Colombia and Latin America.

Cowork Arcetec with Microsoft 365 is the workspace for your whole organization on the Microsoft 365 you already use: shared projects, everything the company has already written just a question away, and deliverables archived where they belong. It is not an assistant you consult: it is where the team works.

• Each person sees exactly what SharePoint already lets them see: it does not expand anyone's permissions.
• Files are archived in your libraries; the platform keeps a pointer, not the document.
• Archiving is a button a person clicks, never a decision made by the agent.

Mesa de trabajo compartida sobre Quarterly operations report: varias personas y el agente de Cowork Arcetec con Microsoft 365 dentro de la misma pieza, cada uno en una sección distinta y viéndose entre sí. En este momento hay varias partes abiertas a la vez: Quarterly figures y Breakdown by area. La pieza terminada se archiva en Your SharePoint. Las fichas son iniciales de ejemplo y no corresponden a ninguna persona.

Working together on what your company already knows.

The meeting minutes, the project sheet, the quarterly report and the email where everything was agreed already exist, scattered across SharePoint, the mailbox and the memory of three people. What is missing is not information: it is a place where the team and AI can use it at the same time.

• Works where your information already is — There is nothing to upload and no need to migrate the repository to another tool. The platform reads the SharePoint libraries your team already maintains (and the corporate mailbox, if the organization turns it on) and returns the deliverable to the folder you specify.
• Your brand applies itself — A brand is defined once (two colors and the logo) and every piece comes out with it. There are no templates to update by hand and no old versions of the logo circulating through the team's emails.
• For the whole organization — Everyone signs in with their corporate account, and projects are shared with the right people. One person's work becomes the starting point for the next, and it stays where the team can find it.

A project is the unit of work.

Each project keeps what would otherwise have to be explained again in every conversation: who works on it, where its output is archived, which brand it uses and what the agent should keep in mind. It is shared with the right people, and the conversations stay inside it.

• Its people — The project is shared with the people in the organization who work on it, and from then on one person's work is the starting point for the next. Whoever created it decides who joins, who leaves and when it is archived.
• Its destination folder — Each project points to the SharePoint library and folder where everything it produces is archived. Nobody has to remember where each thing went, or search for it two weeks later.
• Its brand — The project carries the brand its pieces come out with. A business group or an agency can work for several brands at once without switching tools or maintaining duplicate templates.
• Its instructions and skills — What the agent needs to know in that project is written once: instructions, guidance documents and custom skills. The conversation starts with the context already in place, not with half a page of background.

Everything is kept, and that is why it can be found.

The conversation from three months ago where something was decided does not depend on someone remembering it: it is indexed.

Every conversation and every project stays in your instance, and the search engine goes through them in two ways at once: by the exact words someone wrote, and by meaning, for when nobody remembers how it was phrased. The results from both paths are combined into a single list. The meaning-based path uses a model that runs inside your own instance: your company's text is never sent to an external service to be indexed. And there is a keyboard shortcut that opens the same search from any screen: SharePoint documents, conversations, projects and brands, in a single box.

• By exact words and by meaning, at the same time
• The index is computed inside your own instance
• Finds conversations and projects too
• A keyboard shortcut opens it from any screen

All of what was discussed, indexed

From project to archive, without leaving the conversation.

1. Step 01 · A project is opened and shared — Each project carries its destination folder, its brand, its instructions and the people who work on it. Nobody has to explain the context from scratch again.
2. Step 02 · Questions are asked about what already exists — The agent searches the SharePoint libraries, and the mailbox if it is turned on, with the access of the person asking: no more and no less than what that person already sees.
3. Step 03 · The team and the agent work at the same time — Several people inside the same piece, each on their own part, with the colors and typography of the chosen brand and without overflow or substituted fonts.
4. Step 04 · The piece is archived where it belongs — Someone reviews the result and archives it with a button, in the library and folder they choose. The agent does not upload anything on its own.

Your repository is still your repository

The question at the first meeting is always the same: “so where does this store the files?”

In your SharePoint. The platform does not create a parallel repository or ask you to upload documents somewhere else: it reads and writes in the libraries your team already maintains, with the site and folder structure that already exists. The agent's tools use the delegated access of the person in the conversation. In other words, each person sees exactly what they already see in SharePoint, not one document more. Being a platform administrator does not expand anyone's access to SharePoint. It is worth being precise about what stays on each side. The files are yours and stay in your libraries: the deliverable is just another file in the right folder, with its version history and inherited permissions, and only a pointer remains on our side. The work lives in your instance: the conversations, what the assistant read during them so it can pick them up again, the content of the deliverables with their history, the instructions and the skills. That is precisely what makes search possible, and it is deleted when you delete it.

• No parallel repository: these are your usual libraries
• Delegated access: everyone sees what they already saw
• Files in your SharePoint; the work in your instance
• The agent uploads nothing unless someone clicks the button

Explorador de SharePoint dentro de Cowork Arcetec con Microsoft 365: el sitio Comercial, la biblioteca Documentos y la carpeta Propuestas, con el entregable recién generado archivado entre los documentos que ya estaban allí.

Email is also company memory.

Half of operations were agreed by email, and that is where they still are: the accepted price, the change in scope, the date that moved. If the organization turns it on, the agent can look it up with each person's permissions.

• With each person's permissions — Queries use the Microsoft 365 delegated access of the person asking. Nobody finds an email they would not find by opening their own mailbox, and anyone without an indexed mailbox does not have this capability in their conversations.
• Off by default — It does not come turned on. An administrator in your organization turns it on when they decide it makes sense, and can turn it off again. Indexing a mailbox stores the subject, body and attachment text in your instance, and that is exactly what makes it possible to find them later.
• Reads, does not write — The permission requested from Microsoft is read-only. The platform does not send email on anyone's behalf or reply for anyone: that capability does not exist in the product, so it is not a policy someone could change.

You teach it once and it applies it every time.

A company's way of working does not fit in one conversation, so there is no need to explain it in every one.

• General instructions, plus instructions for each project
• Guidance documents in Word, PDF, Markdown or text
• Company and project skills, with the project's taking precedence
• Scripts included in a skill are stored, not executed

There are three layers, and they apply together. Instructions tell the agent how to behave, for the whole company or only within a project. Guidance documents are reference material (a manual, a policy, a template) uploaded in Word, PDF, Markdown or plain text, which the agent opens when needed. And skills are specialized instructions for a specific task: how a report is written at your company, what goes into a project sheet, what gets checked before something is considered finished. When a company layer and a project layer overlap, the project's takes precedence: the organization sets its standard and each team adjusts it without asking for permission. One limit worth stating up front: if a skill includes scripts, they are stored for reference and never executed. What the platform incorporates is written judgment, not programs.

Five engines, not five templates.

A presentation is presented, a document is read, a spreadsheet is filtered, a diagram is looked at and a repository is unzipped. They are not variants of the same file, which is why each one has its own engine and its own formats.

• Presentations — A fixed canvas with absolute coordinates and per-field limits calibrated to fit on the slide. The PDF is the client deliverable; the PPTX comes out with native objects (shapes, text boxes, tables, charts with data) so it can be edited and presented.
• Documents — A4 with paragraphs that flow and paginate properly, not boxes that overflow. The limits are semantic: a table can hold thousands of rows because the text paginates. The DOCX comes with native Word styles, lists, tables and table of contents.
• Spreadsheets — A sheet with its columns and formats, in Excel to work in and in Markdown to review in a ticket. It is the format for the trackers, inventories and dashboards that are put together by hand every month today.
• Diagrams — A flow, layers, a timeline or quadrants, in the brand's colors. They draw structure, not illustrations. The PNG comes out at double density for screens and the SVG scales without losing sharpness.
• Code — A file tree with its paths, in ZIP to unzip and in Markdown to review in a ticket. Twenty-nine languages, and those that run against an engine declare which one. The agent writes but does not execute: it does not compile, install or test. The one who decides to run it is a person who has read it.
• Connectors and integrations — If operations live in another system, it is registered as a connector and the agent can query it: open or credentialed MCP servers, and already integrated APIs such as Alegra and Granola. The credential can belong to the company or to each person, and it is added by an administrator: the model cannot register any.
• Admin console — Brands with their accessibility panel, users and roles, session revocation and a log of everything that happened. Setup is done through a first-run wizard, with no environment variables or files to edit.
• Artificial intelligence included — Artificial intelligence is included: Claude models in Microsoft Foundry, on Azure, with a credit every month.

Nine formats, each with its role

Which one goes out and which one stays inside is not a detail: it decides whether a piece looks the way it was intended.

Panel de entregables de Cowork Arcetec con Microsoft 365: una presentación, un documento, un diagrama y un repositorio de código ya archivados, cada uno con la marca con la que se generó y los formatos en los que se entrega.

The PDF is the deliverable: it is the only format that guarantees that whoever opens it sees exactly the typography and layout that were designed. If the brand font did not load, generation fails instead of silently substituting it. The editable formats are for internal work. DOCX cannot embed fonts (it is a limitation of the Word format, not a choice), so if whoever opens it does not have the font, Word substitutes it without warning. That is why the document that goes out is always the PDF.

• PDF: for external use, with guaranteed typography
• PPTX: for presenting and editing, with native objects
• DOCX: for internal editing, with Word styles
• XLSX: the sheet with its columns and formats
• Markdown: for a ticket or a code review
• PNG and SVG: for an email, a slide or enlarging
• ZIP: the code project, ready to unzip
• And the single file (a.sql, a.py) when the code is just one

How it is delivered, and what is needed on your side

It is a service, not software you install. This is exactly what Arcetec operates and what remains yours.

Reparto del servicio en dos zonas: de un lado, Operated by Arcetec —la instancia dedicada, las actualizaciones y el soporte—; del otro, Still yours —el tenant de Microsoft, los documentos y la información—, conectados por un registro de aplicación que autoriza un administrador del cliente y que puede revocar cuando quiera.

Cowork Arcetec with Microsoft 365 runs in Arcetec's cloud, in a dedicated instance for your organization: its own deployment and database, without sharing space with any other client. Arcetec takes care of the infrastructure, updates, backup and monitoring. People sign in through the browser with their corporate account, from a computer, tablet or phone. There is nothing to install and no specific device where the work lives: what was left half-done at the office can be picked up at the airport. On your side, you need a Microsoft 365 tenant and an administrator to authorize the application. If you do not have one, or have no one to manage it, we create it in your company's name and operate it for you.

• Your dedicated instance, not a shared space
• Requirement: a Microsoft 365 tenant and an administrator to authorize it
• If you do not have one, we create it in your name and manage it
• From the browser: computer, tablet or phone
• Monthly fee by plan; no-cost setup with a one-year contract

Cowork Arcetec with Microsoft 365 in four figures

What usually decides whether an AI tool makes it into operations or stays a pilot.

• 5 — Distinct engines: presentation, document, spreadsheet, diagram and code
• 9 — Delivery formats, each with a defined role
• 29 — Programming languages the code engine writes
• 7:1 — Minimum contrast guaranteed in every branded piece (WCAG AAA)

What a technology committee asks first.

The answers are not policies written in a document: they are properties the code enforces, which is why they can be verified in a demo.

• Encrypted secrets, never in a file — There is no configuration file with credentials. Everything is defined in the console and stored encrypted, with a master key that is the only thing that lives outside the database.
• Delegated access to SharePoint — The agent's tools use the access of the authenticated person, not a service account with broad permissions. Being a Cowork Arcetec with Microsoft 365 administrator does not open a single additional document in SharePoint.
• The agent does not write to SharePoint — Archiving is a separate call, triggered by a button with the destination path in view. Not even an instruction hidden inside a client document can trigger an upload.
• Files do not stay with us — Deliverables are produced in memory and uploaded to your SharePoint; only a pointer (library and identifier) remains on our side, and downloading them fetches them from there again. What does live in your instance is the work: the conversations, what the assistant read in them, and the content of the deliverables with their version history.
• Entra ID, roles and revocable sessions — People sign in with the corporate accounts your team already manages. There are administrator and read-only profiles, and any session or token can be revoked instantly from the console.
• A log of everything that happened — Every configuration change, every connector added and every archiving action is recorded: who did it, what changed and when. Auditing is not a separate module that has to be turned on.

Your brand, applied automatically and without exceptions

Accessibility is not checked at the end: it is derived at the start, which is why there is no way to skip it.

Panel de marca de Cowork Arcetec con Microsoft 365 para Comunidad: cada color de identidad con el token de texto derivado y su relación de contraste medida contra el fondo claro y el oscuro, todos cumpliendo el nivel AAA.

A brand is defined with two identity colors and its logo. From there, the shades that carry text are derived until they reach AAA level (seven to one) against the actual backgrounds of each theme, light and dark. The difference from checking accessibility at the end is that here there is no write path that allows an inaccessible palette to be saved. It is not that the system warns you: that state simply cannot be reached. And the pieces inherit that palette without anyone having to remember. Several brands coexist in the same deployment, so an agency or a business group can produce for each one without switching tools or maintaining duplicate templates.

AAA The level that is derived, not checked

We built it for ourselves before selling it.

Cowork Arcetec with Microsoft 365 was born because our own team was working blind: what we needed was in SharePoint and in email, and nobody could find it when they needed it. Everything on this page is in internal use.

• Nothing to operate — The platform runs in Arcetec's cloud, in a dedicated instance for your organization. Infrastructure, updates, backup and monitoring are on our side.
• Not shared with anyone — Its own deployment and database. No other company shares space with you, and your brands and templates do not sit alongside anyone else's.
• Designed for groups and agencies — Each brand with its palette, logo and permissions. A business group or an agency produces for all its clients without duplicating templates or installations.
• We implement it — Arcetec installs it, connects the Microsoft 365 tenant, defines the brands with your marketing team and trains the people who will use it. We do not hand over a repository and wish you good luck.
• Support in Spanish, on Colombia time — A team in Cundinamarca that responds in your time zone, with response times committed in writing and support hours included according to the plan.
• No one gets locked in — Everything the platform archives goes to your libraries from day one. If you leave the service tomorrow, there is nothing to export or request from us: the files are already where they always were.

Questions we get asked before signing.

What a technology committee and a marketing team usually want to settle at the first meeting.

This is also part of the same story.

The other pages in this line, so you can continue wherever is most relevant.

Microsoft 365

• Microsoft 365 for business — Exchange, Teams, SharePoint, Entra ID and Intune, well governed.
• Microsoft 365 Copilot for Business — Get more out of Microsoft 365 Copilot in your company with role-specific use cases. Increase productivity and real adoption of the tool.
• LMS on Microsoft 365 — Corporate training inside the Microsoft 365 you already pay for.
• Cowork Arcetec with Microsoft 365 — Your team and AI working on your Microsoft 365.
• Microsoft Licensing — Microsoft 365, Copilot and Azure through CSP, invoiced in pesos.

Arcetec's own solutions

• Our own solutions — The applications Arcetec develops and deploys inside the Microsoft 365 your company already pays for: your people sign in with Entra ID and documents live in your SharePoint.
• CataAI — AI developers who receive their cases by email and Teams, plan them in Azure Boards and carry them all the way to production.
• Lienzo — Social media pieces with your company's brand.
• Licitaciones AI — Licitaciones AI streamlines SECOP II monitoring, optimizing the search for opportunities and making proposal submission more efficient.
• Comunidad360 — Access, bookings, resident census and requests for your community.
• Planeo360 — Projects, clients, resources and help desk in one platform.

Two ways to work with us

We work in two ways, and this is one of them. Our own products are a service that Arcetec operates on its own cloud, with a dedicated instance for each client. There are no servers to manage and no updates to apply. Azure projects work the other way around: they are deployed in the client's subscription, with its own billing and keys. If what you are looking for is your own infrastructure rather than a service, that is the line for you.

How long does it take today to find what your company has already written?

Schedule 30 minutes. We work live on a real case from your team, and you leave the meeting with an effort and cost estimate for your case, not a generic proposal.

Schedule your Cowork Arcetec with Microsoft 365 demo

Tell us how your team works today and we will contact you within one business day to arrange the demo.