Modules
Plugins
Plugins add third-party tools to your workspace, from small widgets to full apps. Each plugin runs isolated from Tylode and can only do what you explicitly allow when you install it.
How plugins work
You'll find them in Settings → Workspace → Plugins (click your name in the top bar, then Settings). There you install, open, pin and uninstall them. You can also go there directly at app.tylode.com/dashboard/settings/extensiones.
- A plugin is a small web app loaded from its own address, inside an isolated frame. It can't see your session, your password or the rest of the screen.
- It can only ask Tylode for data through the permissions it was given when it was installed. Anything else is refused.
- A plugin acts as the person using it: it only ever sees what that person can see in Tylode, and within that, only what its permissions allow.
- Plugins are installed per workspace, not per account. Everyone in the workspace sees the same installed plugins.
- Plugins work on every plan, and there's no limit on how many a workspace can install.
The catalog
At the top of Plugins, people who can install plugins see the Catalog: plugins reviewed by Tylode.
- Use this one fills in the install form below with the plugin's name, address and the permissions its author requests. You review them and confirm before installing.
- More info opens the author's page.
- Official marks plugins made by Tylode, and Already installed those you already have.
Right now the catalog has Hello Pages, an official example that lists the workspace's pages and creates new ones. It asks for "Read your pages" and "Create and edit pages". It's also a good starting point if you want to build your own.
Install a plugin from a URL
- In Plugins, click Install plugin.
- Give it a Name.
- Paste its address in Plugin URL (loaded in an isolated iframe). It must start with
https://, point to a public server and weigh less than 2 MB. - Under Permissions, tick only what the plugin needs.
- Click Install.
If the address isn't valid you'll see why, for example "The URL must be https and point to a public server." or "The plugin is larger than 2 MB."
Plugin permissions
Each permission lets the plugin do one thing on behalf of the person using it. "Your" in the labels means that person.
| Permission | What the plugin can do |
|---|---|
| Read your pages | See the workspace's pages: titles and content. |
| Create and edit pages | Create pages and change their title and content. |
| Read your boards | See boards and their cards. |
| Create and move cards | Add cards to boards. |
| Read your calendar | See the events of the workspace calendar. |
| Create and edit events | Add events to the workspace calendar. |
| Read your whiteboards | See whiteboards and the items on them. |
| Create items on whiteboards | Create whiteboards and add sticky notes, text and shapes. |
| Read your presentations | See your Studio presentations and their slides. |
| Create slides | Create presentations and add blank slides. |
| Read your conversations and their messages | Read your chats. |
| Write messages on your behalf | Send chat messages as you. |
| Read your internal mail | Read your mail threads. |
| Write and reply to mail on your behalf | Send and reply to Mail messages as you, and mark threads as read or archived. |
| Read and download files from My drive | List and download your My drive files. It can't upload or delete. |
| Read your notifications | See your notifications. |
| Mark your notifications as read | Mark your notifications as read. |
| Search your entire workspace | Search pages, boards, whiteboards, presentations, mail and chat messages. |
No permission gives access to databases, so plugins can't read or change them.
Open a plugin
Installed plugins appear as cards on the Plugins page, with the number of permissions they have. Click one to open it on its own page.
Pin a plugin as a side panel
A pinned plugin stays open on the side of the screen while you move around Tylode.
- Hover over the plugin's card on the Plugins page.
- Click the pin (Pin as side panel: it stays open while you browse).
In the side panel you can:
- Drag its edge to change the width (Drag to change the width).
- Click Collapse to fold it into a narrow tab with the plugin's name. Click the tab to open it again.
- Click Unpin this plugin to close it for good. You can also use Remove from side panel on the plugin's card.
You can pin one plugin at a time. Pinning is personal: it only changes your screen, and Tylode remembers it on all your devices. The side panel only appears on wide screens; on phones and narrow windows, open the plugin from Settings → Workspace → Plugins instead.
Uninstall a plugin
- Hover over the plugin's card and click the bin (Uninstall).
- Click it again within three seconds to confirm.
The plugin is removed for the whole workspace.
When a plugin's code changes
When a plugin is installed, Tylode saves a fingerprint of its code. If the address later serves different code, you'll see a banner on the plugin: "This plugin's code has changed since it was installed." The permissions were granted to the code that was there before, so review what changed before you keep using it.
- Trust the current code saves the new fingerprint and hides the warning.
- Not now hides the banner for the moment.
Plugins installed before Tylode saved fingerprints show "This plugin has no saved code fingerprint." instead. Click Trust the current code to start watching them.
Who can install plugins
Installing, uninstalling and trusting new code need the Manage plugins permission. Owners and admins have it; you can also give it to others with a custom role (see roles and access).
Everyone else sees this note instead of the install options: "Installing and removing plugins is up to admins. A plugin gets permissions over the data of the whole workspace, so it's not an individual decision. You can use the ones already installed." They can open and pin any installed plugin.
Build your own plugin
Plugins are regular web pages that talk to Tylode through a message bridge. To learn how to build one, see Plugins for developers.