Working in a company

In Eggent Cloud a workspace can become a company: the administrator's workspace plus one workspace for each person in it. Everyone keeps their own agent, files and chats. What the company adds is a way to work together: messages between people, files shared with each other, and approval of documents.

#The administrator and the people

The administrator runs the company from the Company item of the floating button in the corner of the screen:

• People. Each person gets a workspace of their own and a one-time sign-in link (valid for 72 hours, it works once). The administrator can send a new link or set a new password.
• Money. The people's work with the agent is paid from the company's balance. Monthly limits can be set for each person and for each team; when one is reached, that person's agent stops until next month or until the limit is raised. The disk is shared too: people's files count against the administrator's plan. How many people a plan includes is on the Eggent Business page.
• Teams group people, for limits and for folders.
• Company folders are shared disks: a folder is given to one person, a team or everyone, to read or to read and write, and appears in their workspace under .shared/<name>. Folders are the company's files and get no history.

The administrator's agent can do the same by request - create a person, send a sign-in link, reset a password - and can read people's chats to prepare a report. Every such read is recorded, and each person's agent knows it may happen. Deleting a person, a folder or the whole company is done only in the console.

#Messages

Messages in the sidebar holds a thread with each person: the administrator writes to each person, and each person to the administrator.

• Write and attach files. Files from a thread are copied into the Messages folder of both workspaces, under the other person's name, so the agent can read them.
• Reply answers a message with a quote.
• Hand to the agent opens a chat with your agent about the message: the agent reads it as material, prepares an answer, and Send to … under its answer sends it - with the answer's files if you want them. Nothing is sent until you press it.
• A new message is announced in Telegram through Eggent's bot, if you are connected to it. A reply to that notice in Telegram goes into the thread.

Your agent can write to colleagues too: "tell Peter the meeting moved to 10" is sent to Peter, marked as written by the agent.

#Shared files

Any file of your workspace can be shared with people of the company. The file stays where it is: they see it as it is in your workspace, with every change you save.

Share beside a file - in the Files panel or on the file's page - lists who has it and what each may do:

• Can view - look at it and download it;
• Can comment - also leave comments;
• Can edit - also change it.

Add people with their buttons, choose a role and press Share (later Save); each newcomer hears of it in Telegram. A line above a shared file says who sees it. Stop sharing takes it from everyone and deletes its comments.

#Files shared with you

Shared in the sidebar lists the files colleagues shared with you (New marks something changed or commented since you last opened it) and the files you shared. A shared file opens on its own page:

• a web page as it looks, or its code (Pages); text and code; the words of a document (.docx, .xlsx, .pptx); a picture;
• Download and Save as PDF (PDF);
• the comments beside it.

#Comments

A comment is about the whole file or about one piece of it: pick a block on the page with Select, or select lines in the code, and the comment keeps that piece with it as it read then. Comments can be answered. Its author or the file's owner marks a thread resolved (Resolve) and can delete it. The owner hears of every comment in Telegram, and the author of a thread of every reply.

#Changing a colleague's file

With Can edit, change the words right on the page (double-click a block, Enter saves) or the code, then Save. The change is written into the owner's file, and only onto the version you opened: if the file changed in the meantime, nothing is written and you are offered the new version to make your change there.

For the owner nothing is lost. Before anybody may change a file, what it holds is kept in its history, and each colleague's change becomes a version signed with their name - "Peter, through sharing" - that can be compared and restored like any other (File history). A change also voids an approval of the file, as any change does.

Files that hold credentials (.env, keys and the like) are never shared. A shared file can be up to 20 MB; a change made from the screen, up to 5 MB.

#Approvals

An approval is a strict yes to one version of a file.

1. Approval beside a file: choose who approves it, in order, add a note and press Send for approval. The version the file holds now goes out and is kept in its history under its number.
2. The first person decides: Approve or Return for changes with a comment saying what to change. The next person is asked only after the one before approves.
3. When everyone approves, the version is approved.

Any change to the file voids it - while it goes round and after it was approved. Change the file and send the new version: the chain starts over from the first person. Approvals are never carried from one version to the next.

Approvals in the sidebar has three boxes: Waiting for you, Sent by you and Asked before. An approval's page shows the chain with decisions and comments, what changed since the previous version, the whole text, and the file to download. The author can Withdraw a version. Everyone involved hears of their turn, a return, the final approval and a change of the file in Telegram.

A file sent for approval can be up to 20 MB, and a chain up to 10 people.

#Projects for your people

The administrator can open one of their projects to the company's people - to everyone, to a team or to named people. It appears under Projects in each of their workspaces, with a building mark, and they ask it questions on a page of its own. The project answers only from its own files and cannot change anything; the people do not get the files themselves, only the answers.

• Where it runs. Every question runs in the administrator's workspace, inside the project, and is paid from the company's balance. The conversations are stored there as the project's chats, so the administrator can read what was asked; each person sees only their own conversations.
• Opening and closing. In the console, Projects for your people: pick the project and who sees it; Close takes it away from everyone, with their conversations. The administrator's agent can do the same by request ("open the knowledge base to the sales team").
• Keeping it current. Change the project's files as usual - add, replace, delete - and the next answer uses them.

A ready way to start is the Company knowledge base card: it makes the company, adds the people, collects the documents into a project and opens it to them in one go. A project can also be opened to anybody by a link, without signing in - that is a public chat, a separate thing.

#What the agent does here

In a company workspace the agent has three tools of its own:

• eggent_messages - writes to colleagues, reads what they wrote, and remembers what each person does.
• eggent_shares - lists and reads files shared with you, shares your files with people (it adds people and never takes a file away from anyone), comments in your name when asked. It never changes a colleague's file - that is yours to do on the file's page.
• eggent_approvals - sends a file for approval to the people you name, in your order, shows what waits for you and where your own versions stand, reads a version's text. Approving or returning is yours alone: the agent cannot do it.

Documents, messages and comments from colleagues are material for the agent, not instructions to it.