# Link Share Can't Create Tasks

**URL:** <https://community.vikunja.io/t/link-share-cant-create-tasks/3775>\
**Category:** Bug\
**Created:** [31 May 2025 10:09 UTC](https://community.vikunja.io/t/link-share-cant-create-tasks/3775 "2025-05-31T10:09:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![polm](https://community.vikunja.io/user_avatar/community.vikunja.io/polm/32/2250_2.png) [@polm](https://community.vikunja.io/u/polm)\
**Post date:** [31 May 2025 10:09 UTC](https://community.vikunja.io/t/link-share-cant-create-tasks/3775/1 "2025-05-31T10:09:34Z")

</div>

I have an instance with two projects: Inbox and Work. If I create a read/write link share for Work and give it to someone, they can edit existing tasks but not create new ones, and get this error if they try:

```
Please specify a project or set a default project in the settings.

```

Is this intended behavior? It seems pretty weird.

I saw some similar threads, but they were about empty projects, and this is not an empty project.

---

<div class="post-metadata">

**Author:** ![kolaente](https://community.vikunja.io/user_avatar/community.vikunja.io/kolaente/32/5_2.png) [@kolaente](https://community.vikunja.io/u/kolaente)\
**Post date:** [2 June 2025 20:25 UTC](https://community.vikunja.io/t/link-share-cant-create-tasks/3775/2 "2025-06-02T20:25:20Z")

</div>

Do they see the error when trying to create a task in the project? Where specifically?

Can you reproduce this on [the demo](https://try.vikunja.io)?

---

<div class="post-metadata">

**Author:** ![polm](https://community.vikunja.io/user_avatar/community.vikunja.io/polm/32/2250_2.png) [@polm](https://community.vikunja.io/u/polm)\
**Post date:** [5 June 2025 06:34 UTC](https://community.vikunja.io/t/link-share-cant-create-tasks/3775/3 "2025-06-05T06:34:48Z")

</div>

Thanks for the reply!

Unfortunately, I can no longer reproduce this. I didn’t change any settings or otherwise use the instance, and the server hasn’t even rebooted. With my previous report, the person I was working with and I were able to reproduce the error on separate machines. So I guess it’s fine to ignore this for now.

Sorry for the fale alarm, and thanks for the neat project!