Sure thing! Setting Cross Project Dependencies is easy.
If you mean that tasks on Project A can influence the schedule of tasks on Project B, then yes. We call those Cross Project Dependencies and you can read about them here:
Now, sometimes we see that teams over-use the Cross Project Dependencies and it creates all sorts of nasty things like circular references, or complicated looking predecessor columns of the task lists, or "having a devil of a time trying to find the reason why your schedule wants to start this task way the heck out there!" ... Just as a few examples.
There are no visual references that will show you Cross Project Dependencies. These dependencies do not show up on a Gantt chart anywhere. There only one place that you will see the Cross Project Dependencies will be on the task list in the predecessor column.
If you visited this page due to the Newsletter we just sent out, let me know in the comments below! If you don't know what I'm talking about when I say "newsletter," then you missed out because the newsletter was awesome! It was also our first one, so let's chat in the comments below.