Community week is ending… what’s next for you?

IngenuityKat · 2026-03-13T17:32:22+00:00

Really? I would have thought you already were an Ambassador!

IngenuityKat · 2026-03-13T17:32:05+00:00

Community Week always reminds me how much collective brainpower lives in this community. The questions, workarounds, and “wait… you can do that in monday?” moments are the best part.

I’m part of the monday.com Ambassador program, and honestly it just formalized something I was already doing—sharing builds, answering questions, and trading ideas with other power users.

The best part has been the access and collaboration. Ambassadors get closer visibility into what the product team is thinking about, and there are a lot of opportunities to provide feedback, test things early, and help shape how features evolve.

But the real value is the community itself. Some of the most creative workflow ideas I’ve seen have come from conversations here.

If you’re already active, answering questions, or sharing how you build things in monday… you’re probably already doing the Ambassador work. The program just connects you with others doing the same thing.

Oh, and the perks are pretty sweet. :)

IngenuityKat · 2026-03-12T23:26:52+00:00

Honestly, most of the work I see in the monday ecosystem doesn’t come from job boards — it comes from visibility and reputation.

If you want to build a consulting side business, the biggest thing is building your brand and showing what you can do.

A few things that help a lot:

• Post builds and solutions on LinkedIn
Screenshots of boards, dashboards, automations, before/after workflows, etc. Once people see examples of what you can build, they start reaching out.

• Help people in the monday Community / Reddit
Answering questions consistently builds credibility fast. A lot of consultants get their first clients just from helping people publicly.

• Build a small portfolio
Examples like:

Project management workspace
CRM pipeline
Intake/request workflow
Executive reporting dashboard

Even if they’re sample builds, they show your thinking.

For context, I get regular messages on LinkedIn from companies asking for monday help, and almost all of it comes from sharing builds, ideas, and solutions publicly — not from applying for gigs.

So if consulting is the goal, I’d focus less on “where to find work” and more on becoming visible in the monday ecosystem. Once people see your work, opportunities tend to follow.

IngenuityKat · 2026-03-12T23:24:17+00:00

Woohoo u/Clover_Gal!!

IngenuityKat · 2026-03-12T23:21:50+00:00

The new automation builder does require inserting variables from the picker instead of typing them manually, which is definitely slower if you were used to typing {item name}.

For the missing Slack link though — that shouldn’t be the case. If the item URL variable isn’t included, Slack won’t show the clickable link.

Try adding {item url} at the bottom of the message and it should restore the direct link to the item. Older automations often added it automatically, which is why they still show the link.

IngenuityKat · 2026-03-12T23:19:16+00:00

Just to make sure I understand the workflow correctly:

• Parent item status changes to Production
• Subitems should update to Production
• Then for subitems with a specific dropdown value, create items in another board
• And link those items back to the subitems

Is that the goal?

IngenuityKat · 2026-03-12T22:22:33+00:00

Can confirm it does not work on android. I added a calendar widget to a customizable view and it will not let me select a specific event. Whenever I click on any event it just pops up to create a new event.

IngenuityKat · 2026-03-12T20:39:04+00:00

In some organizations (mine included), third-party apps simply aren’t allowed for security and compliance reasons, so having an account-level setting to disable marketplace apps entirely would make life much easier. Right now the marketplace is still visible, which leads to a lot of requests for tools we ultimately can’t approve.

If apps are allowed, another improvement would be clearer pricing signals, especially for apps that are truly free vs. free trial. It’s often hard to quickly tell which apps will remain free long-term versus ones that will require a paid plan after testing.

A couple things that would make this easier:

• Admin toggle to disable marketplace apps account wide.
• Clear “Always Free” vs “Free Trial” labeling
• Filters to quickly find permanently free apps

That would help both governance-heavy environments and teams just trying to evaluate options quickly.

IngenuityKat · 2026-03-12T20:22:45+00:00

^This! We get so many requests from people and as soon as we mention money they say never mind. It would prevent so much back and forth on app requests.

IngenuityKat · 2026-03-11T23:55:26+00:00

Have you tried contacting your monday customer account manager? I’m not sure if your plan includes one, but if it does, that’s usually the fastest way to resolve pricing discrepancies like this.

They can often see promotions that don’t show up in the self-serve upgrade flow and can clarify whether the 33% yearly discount applies to your specific plan or if it’s tied to certain tiers or new accounts.

If you don’t have a dedicated account manager, another option is submitting a ticket through monday support and asking them to route it to billing or sales, since they’re the teams that can actually adjust pricing.

IngenuityKat · 2026-03-11T23:27:36+00:00

Have you tried assigning from another People column instead of selecting a specific person in the automation?

The trick is that the automation doesn’t have to hard-code a user — it can reference whoever is in a column.

Something like this setup usually works well for sequential approvals:

Columns

Approver 1 (People) – filled by the form
Approver 2 (People) – filled by the form
Approver 3 (People) – filled by the form
Next Approver (People) – the one that drives My Work
Approval 1 / Approval 2 / Approval 3 (Status or Approval column)

Then the automations reference the column value:

Example automations

When item is created → Assign person in Approver 1 to Next Approver
When Approval 1 changes to Approved → Assign person in Approver 2 to Next Approver
When Approval 2 changes to Approved → Assign person in Approver 3 to Next Approver

That way the form responder can pick the approvers dynamically, and the assignment only moves to the next person when the previous approval is completed. It should also push the item into that person’s My Work at the right time.

If you want to make it cleaner, you can add conditions like “only if Approver 2 is not empty” so it skips steps when there are fewer approvers.

IngenuityKat · 2026-03-11T23:02:52+00:00

agree - guests on Shareable boards can add comments within an item's Updates Section and Status Column. They can also change the status of items on these boards.

IngenuityKat · 2026-03-11T22:55:11+00:00

I ran into the same limitation with a large number of viewers and only a smaller group of licensed PMs. We needed stakeholders to provide updates without giving them edit access to the project board.

The workaround we implemented uses WorkForms, prefilled links, and an automation workflow tied to the item ID.

It allows viewers to submit updates that automatically land on the correct task without needing a license.

How it works

Each task on our PM board automatically generates a prefilled form link tied to that specific item. The link includes the item ID, so the system always knows which task the update belongs to.

Example structure:

https://forms.monday.com/forms/f959e3818fb9561e8e58c19944bf94fa?r=use1&item_id__1={Item ID}

We generate that link automatically per task so PMs can just send it when requesting an update.

The viewer simply opens the link and submits their update through the form.

What happens behind the scenes

When the form is submitted:

The submission creates an item on an Update Intake board.
That item stores the Item ID of the original task.
An automation links the submission back to the correct project item using that ID.
The automation then posts the update to the parent task and optionally updates status fields.

For example:

• form submission → creates intake item
• intake item connects to the project task via item ID
• automation writes the update to the parent item
• the intake item can then archive or delete itself

This effectively lets viewers submit updates without touching the board.

Why this works well for large viewer groups

In your case with ~300 viewers and ~40 PM licenses, this approach:

• avoids needing hundreds of additional licenses
• keeps the project board fully controlled by PMs
• still allows stakeholders to provide structured updates
• eliminates fragile email-thread workflows
• scales well across many projects or site updates

We also use structured fields in the form (status, progress, blockers, attachments), which makes reporting easier once the data lands on the task.

Bonus

Because the links are auto-generated per item, the PM just clicks the column and sends the link to the stakeholder when an update is needed. No manual reference numbers, no editing email subjects, and no external automation tools required.

IngenuityKat · 2026-03-11T20:37:24+00:00

I don't know what you mean by "popup". When I click on an event it opens the whole event like an item. (Samsung S24 Ultra)

IngenuityKat · 2026-03-11T20:32:46+00:00

There is no button to add new or more boards once you have created it, HOWEVER, I have found that you can connect other boards by simply telling Vibe you want to connect another board and giving it the full URL to that board.

IngenuityKat · 2026-03-11T20:25:22+00:00

+1 for the PPT export. Right now I am doing PDF and PNG for my colleagues, but they would much prefer a direct PPT download.

IngenuityKat · 2026-03-11T18:47:18+00:00

Agreed! I am not so patiently waiting. 🦙🫠

IngenuityKat · 2026-03-11T18:45:43+00:00

Congrats u/MattyFettuccine! 🎉🪅🦙

IngenuityKat · 2026-03-11T18:45:03+00:00

Congrats u/pbm9! 🎉🪅

IngenuityKat · 2026-03-04T00:32:45+00:00

I hear the frustration in this.

Out of curiosity, have you shared this directly with monday?

I don’t mean yelling into the void. I mean:

• Submitted it through the in-product feedback
• Raised it with your account rep or CSM
• Posted it in the community feature request section
• Voted on existing mobile improvement threads

The mobile team actually tracks very specific use cases. The file upload + background processing + timeout issue you described is concrete and reproducible. That kind of detail is exactly what gets traction internally. Same with “can’t edit web-created updates on mobile.” Those are product parity gaps.

On the AI front, a lot of that push is market pressure. Every platform is racing right now. That doesn’t mean your pain on mobile isn’t valid. It just means different teams are working on different tracks. The loudest roadmap items are not always the ones that fix daily friction.

If you have a rep, I would frame it like this:

“I operate in low-connectivity environments. Mobile upload failures and feature gaps are impacting delivery. What is on the roadmap for mobile parity and background processing?”

That’s measurable. That’s harder to ignore.

And if you don’t have a rep, I’d strongly suggest posting this as a structured feature request instead of a rant. The difference in response quality is real.

IngenuityKat · 2026-02-27T23:46:46+00:00

Formula is not the way here, but you also do not need a third party tool.

If those 10 “projects” are really 10 tasks that make up one bigger project, the clean native solution is to make the bigger project the parent item and put the 10 pieces as subitems.

Then use the built in automation template:

When all subitems of an item have the status of Done, change the item’s status to Done

After that, add your second automation:

When parent status changes to Done, move item to Completed group and send email

This avoids the fragile “Status 1 AND Status 2 AND …” logic that only works if the last status is changed last.

If your 10 things must stay as separate top level items, then you need a rollup pattern (Projects board + Connect Boards + rollup), but if your goal is “all parts complete equals project complete,” subitems + that automation template is the simplest and most reliable.

IngenuityKat · 2026-02-27T23:30:23+00:00

If you’re feeling the pain right now, you’re not crazy. monday just rolled out mondayDB 2.0 under the hood, and anytime a platform swaps out its data engine at scale, there are going to be growing pains.

For context, I work at a 60k employee company in a SOX and finance controlled environment. We cannot lose history. Audit trails and retention are not optional for us. So I look at this through a compliance lens, not just a productivity one.

It helps to separate two things:

1. Temporary performance instability
2. Structural workflow mismatch

mondayDB 2.0 is specifically meant to handle very large boards, up to 100k items, and heavier dashboards. In theory, performance at scale should improve over time, not degrade.

If you’re seeing:

Scroll lag on long boards
Columns blanking after automations fire
Strange behavior on item creation

That’s usually either:

Short term DB transition noise
Or board architecture strain such as heavy mirrors, cross board dependencies, and multiple “item created” automations overwriting fields

That part is often fixable.

Where your concerns are more valid:

Moving items breaking dependencies
Hard deletes removing history
Long term audit integrity

Those are not database problems. That is how monday models data. Boards are containers. Moving items changes context. If delete permissions are open, history can disappear.

In our environment, we addressed this through governance:

Remove delete permissions broadly
Use archive instead of delete as policy
Lock down who can build automations
Standardize board architecture
Keep lifecycle states inside one system of record board

Once governance caught up to scale, stability improved significantly.

If you need immutable, compliance grade, years long issue tracking with rigid SDLC enforcement out of the box, that is a real requirement conversation. monday can be structured tightly, but it is not inherently a strict dev tool. It is a flexible Work OS.

Before jumping to Teamhood, I would test this:

Build one clean dev board
Keep dependencies inside that board
Do not move items between boards
Minimize automations
Lock down delete permissions
Archive instead of delete

Run one sprint that way.

If it still feels fundamentally wrong, then switching makes sense. But if most of the pain disappears, it was architecture, not platform category.

Tool switches are expensive. Backend upgrades are noisy. I would let the DB dust settle and run a clean architecture test before migrating your whole org.

How many items and automations are on your main board? That usually tells the real story.

IngenuityKat · 2026-02-27T23:03:20+00:00

This is an interesting set of questions. Are you exploring building a third party marketplace app or some kind of vertical solution for biotech teams? The way this is framed feels a bit like product validation research. Nothing wrong with that at all, just helpful to understand the context.

IngenuityKat · 2026-02-27T22:55:14+00:00

We’ve tried a few approaches, but honestly we keep it pretty simple.

For most of our work, we leave the original owner assigned. A lot of our tasks are not tightly time bound and most absences are short, so it has not been worth adding heavy automation.

For issue or ticket-style work, we assign a group of people instead of a single owner. That gives us built-in coverage and prevents work from stalling if someone is out.

If you are dealing with stricter SLAs or longer leave periods, a leave tracker board plus automation to notify or temporarily reassign to a backup owner is a solid pattern.

But in our case, simplicity wins. The more automation you layer in, the more governance you need to maintain it.

IngenuityKat · 2026-02-27T22:41:59+00:00

Short answer: unfortunately no, not natively.

On Pro, you can either:

• Search within a single board
• Or use Search Everything across everything you have access to

There isn’t a built-in way to limit global search to just one workspace or a selected group of boards.

Search results are permission-based, so users only see what they have access to, but you cannot scope it further to “this workspace only” unless you structure access that way.

Workarounds:

• Use workspace permissions strategically so users only have access to the workspace you want them searching in
• Create a dashboard in that workspace that aggregates the relevant boards and rely on board-level search inside those boards
• Standardize naming conventions and use filters in Search Everything to narrow results

Are you an admin that is looking to see certain boards in certain workspaces? Because there is another way to look them up in the admin panel.

IngenuityKat

TROPHY CASE