Capability 01
Google Workspace
Sync Google Docs, Sheets, and Calendar directly in your team space.
All features
Resources
Centralize Your Work Resources
Store Google Docs, Sheets, Figma, YouTube, and any other links in a convenient tab accessible to the entire team.
Built for
- Project teams
- Marketing
- PR
- Onboarding
By the numbers
∞
links per project
Easylim CRM
Preview
rich auto-cards
customer data
0
lost links
2025 survey
Everything your team needs — in one window
Keep all the web services you need at your fingertips.
Capability 02
Design & Creativity
Store Figma and other creative platforms in one place.
Capability 03
Navigation & Video
Add YouTube videos and Google Maps for quick access.
Capability 04
Any Websites
Insert links to any web content without restrictions.
How it works
Project Management
Attach spreadsheets with deadlines and budgets from Google Sheets for transparency.
- Design & UI/UX
- Sales Department
How it works
PR Teams
Store links to ad campaigns, analytics, and dashboards.
- Employee Onboarding
- Team Meetings
Deep dive
Project resources — how to build one link hub instead of "find me that Figma"
5 chapters
The classic scene: a new engineer joins, asks where the Figma is, which account has access, where the design doc lives, the brand guide, the Google Drive of references. The tech lead searches Slack — finds 4 messages with different versions. Notion has a stale link. The pinned message points at last November's Figma. Forty minutes lost, and every new hire spends them again. Resources in Easylim is a project tab with all those links — design, docs, dashboards, videos — one URL for the whole team and zero "where's our…?" pings.
01
Розділ
What resources are and how they differ from notes or documents
Resources is a collection of links to external tools, attached to a project: Google Docs, Sheets, Figma, Miro, Loom, Mixpanel, dashboards, internal sites, YouTube tutorials. Easylim doesn't try to replace those tools — it makes them findable.
Difference vs notes: resources isn't for your own writing, it's for links to someone else's content. Notes are "I jotted down a pitch idea". A resource is "the link to the analytics dashboard". Difference vs documents: a document is something you edit inside Easylim; a resource just points outward.
Every resource automatically gets a rich preview: page title, thumbnail (OG image), domain favicon. It's not a flat list of URLs — it's a visual grid of cards where Figma looks like Figma and YouTube looks like YouTube. The team recognises a link in 0.2 seconds, without reading the text.
- Resource = a link to an external tool with an auto-generated rich preview card.
- Don't confuse with notes (your own text) or documents (edited inside Easylim).
- Rich previews = recognition in 0.2 seconds, no URL parsing needed.
project · resources tab
DDrive · Q3 assets
google drive
FFigma · checkout
figma file
NNotion · roadmap
notion page
LLoom · onboarding
loom video
GGitHub · backend
github repo
YYouTube · demo
youtube video
6 of 18 resources＋ paste URL
02
Розділ
How to build a project resource hub in Easylim in 10 minutes
Open the project, go to the Resources tab, click "+ Add". Paste a URL — Easylim reads the OG tags and builds a card with title, description, thumbnail. Nothing to type by hand, except a tag or category.
Categorise: "Design" (Figma, Miro, Adobe), "Docs" (Google Docs, Notion pages, specs), "Analytics" (Mixpanel, GA, custom dashboards), "Video" (Loom tutorials, YouTube, demos). Custom categories work — the goal is that a newcomer knows where to look without asking.
For Google Workspace you can connect OAuth — Google Docs / Sheets / Calendar get richer previews: last editor, last updated, comment count. For Figma — a thumbnail of the actual frame. YouTube embeds via iframe — click the card and it plays inside Easylim, no tab-switch.
- Paste URL → finished rich card in 0.5s. No manual data entry.
- Categories (design / docs / analytics / video) = "where to look" without asking.
- Google and Figma OAuth → richer previews with metadata (who edited, when).
embed · Figma frame
▶
figmaCheckout v2 · iOS Safari
12 frames · last edited 2h ago by Mia
opens inlinefigma.com/file/checkout-v2
03
Розділ
Embeds, privacy, and why not all links are equal
Not every site allows iframe embedding: Stripe, Notion, many dashboards intentionally block it via X-Frame-Options. For those resources you still get the rich card preview, but clicking opens in a new tab instead of embedding. That's fine — you still have a recognisable visual entry and one-click access.
Privacy is per-resource: visible to the whole team, admins only, or specific members. Useful for links to accounting Google Sheets, password manager entries (1Password URLs), or client-restricted dashboards. Don't store passwords themselves in Easylim — store a link to your password manager.
No hard cap on the number of resources per project. But once you have 200, it's a junkyard, not a hub. Healthy range: 15-30 per active project, 5-10 for archived projects. Prune stale links (Figma files that shipped months ago) so the next newcomer isn't lost across nine different design systems.
- Not all sites embed (X-Frame-Options). Card always present, embed not always.
- Per-resource privacy: team / admins / specific members.
- Healthy: 15-30 resources per active project. More than that = junkyard, not a hub.
folder tree · split view
Folders
▾📁Design
▸📁UI · checkout
▸📁Brand
▸📁Docs
▸📁Analytics
▸📁Video
UI · checkout · 3 items
F
Checkout v2 — frames
figma · 12 frames
F
Mobile flow
figma · 6 frames
D
UI assets
google drive
04
Розділ
A real week with a resource hub — what it looks like
Monday. A new engineer joins. Instead of 40 minutes spent answering "where's the Figma, where's the API spec, where's the dashboard", the tech lead sends one link to the Resources tab. 10 minutes and the newcomer has everything: invited to the Figma file, knows where to read the spec, has the Mixpanel dashboard open.
Tuesday. Client call about a new feature. The PM opens Resources and pulls up three cards: the Figma mockup, the product spec, the Loom demo. Three clicks instead of the Slack/email archaeology that would've taken 15 minutes.
Wednesday. Design review. The designer screen-shares the Resources tab → Figma card → it's embedded, so you can flip frames without leaving Easylim. Task discussion (other tab) and visual review (Resources) — one window.
Thursday. A frontend engineer realises the API spec link is stale (new endpoint added). They update the Resources entry once — the new version is visible to everyone. In the old world this would be 4 Slack messages "here's the new version" and two people still using the old one.
Friday. The PM opens Resources, sees 8 entries nobody opened in 3+ months. Archive the old Figmas and videos. The hub stays clean — the next newcomer won't drown in noise.
- Onboarding = 10 minutes instead of 40. One link instead of Slack archaeology.
- One resource URL → client call in 3 clicks instead of 15 minutes of searching.
- Update a link once → everyone sees the new version. No stale copies in Slack pins.
search resources
⌕checkout⌘K
all18link8file6embed4
F
checkout Figma ·
figma.com
D
checkout brief — Q3
docs.google.com
05
Розділ
When resources isn't the right tool — and what to use instead
If you want to record your own thoughts (an idea, meeting minutes, throwaway notes), that's notes, not resources. Resources is links to someone else's content; notes is your own text. Don't use Resources as a Notion-page substitute.
If you're writing long-form documentation (a user guide, an ADR, a 20-page project spec), that's documents — edited inside Easylim. You can drop a link to that document into Resources, but the document itself lives separately with version history and comments.
If you need a team knowledge base with search, tags, hierarchy (rather than a flat list of 30 links), Easylim works better with notes + documents inside a project than with Resources. Resources is a fast project hub, not an enterprise wiki.
Summary: link to external tool → Resources. Your own text → notes. Long-form editable doc → documents. Don't mix — otherwise a year later you have three places with the same content and nobody knows which is the truth.
- Your own text / idea / meeting minutes → notes, not resources.
- Long-form documentation → documents (with history, comments); link to it from Resources.
- Enterprise wiki → not Resources. Resources is a fast project hub.
resources vs bookmarks
RResources
Team-shared project hub with rich previews.
👥visible to whole team
🖼rich preview cards
📂categorised + searchable
★Bookmarks
Personal browser links — only you see them.
🔒personal · device-bound
🔗plain URL, no preview
📭no team visibility
team-shared → resources · personal → bookmarks
Quick takeaways
- 1Resources = project tab with links to external tools + rich previews.
- 2Paste URL → ready card. Categories = "where to look" without asking.
- 3Healthy range is 15-30 resources per active project. Prune stale ones.
- 4Don't confuse with notes (your own text) or documents (long-form editable content).
Integrations
Plug in the tools you already use
This feature connects to the apps your team already lives in.
- Google Workspace
- Figma
- Notion
- Loom
- Dropbox
- Slack
Frequently Asked Questions:
More features
Explore neighbouring capabilities
Ready to try?
First project in 5 minutes
No card required. Free tier forever.